In some contexts is unclear why an autoscaling policy decides to request
more resources, i.e. if there's an unassigned shard that remains unassigned
even after adding more resources. It would be help to have more information
around the decisions taken by the deciders so it is easier to understand and
track them.
x-pack/plugin/autoscaling/src/main/java/org/elasticsearch/xpack/autoscaling/storage/ReactiveStorageDeciderService.java
if (inNodes.contains(true)) {
                    return true;
                }
            }
            return false;
        }
        
        ClusterState state() {
            return state;
        }
        ClusterInfo info() {
            return info;
        }
        private static class ExtendedClusterInfo extends ClusterInfo {
            private final ClusterInfo delegate;
            private ExtendedClusterInfo(Map<String, Long> extraShardSizes, ClusterInfo info) {
                super(info.getNodeLeastAvailableDiskUsages(), info.getNodeMostAvailableDiskUsages(), extraShardSizes, Map.of(), null, null);
                this.delegate = info;
            }
            @Override
            public Long getShardSize(ShardRouting shardRouting) {
                Long shardSize = super.getShardSize(shardRouting);
                if (shardSize != null) {
                    return shardSize;
                } else {
                    return delegate.getShardSize(shardRouting);
                }
            }
            @Override
            public long getShardSize(ShardRouting shardRouting, long defaultValue) {