-
Notifications
You must be signed in to change notification settings - Fork 24.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose forecasted and actual disk usage per tier and node #93497
Conversation
Documentation preview: |
Pinging @elastic/es-distributed (Team:Distributed) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (one docs nit, one passing thought)
Where `actual_disk_usage` is computed using shard sizes from cluster info only | ||
and `forecast_disk_usage` uses shard size forecast when available. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We really want to document the whole structure of the response, but we can do this when the API is no longer /_internal/...
. For now, I think it would be better to remove these lines.
@@ -155,31 +170,43 @@ public XContentBuilder toXContent(XContentBuilder builder, Params params) throws | |||
} | |||
} | |||
|
|||
public record NodeBalanceStats(int shards, double forecastWriteLoad, long forecastShardSize) implements Writeable, ToXContentObject { | |||
public record NodeBalanceStats(int shards, double forecastWriteLoad, long forecastShardSize, long actualShardSize) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that I think about it, it'd be awfully nice to see the watermarks in these stats too!
No description provided.