-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Indices stats API should provide external refresh stats #36712
Comments
Pinging @elastic/es-distributed |
@clandry94 could you clarify how the change to the stats API differs from the statistics returned by (I'm ok with adding more stats to distinguish the two kinds of refresh as you describe, but that doesn't seem to be the main proposal here) |
Hey @DaveCTurner. I wasn't aware of the |
I do not know this code intimately, but tracing through rather naïvely it seems they are internal refreshes: elasticsearch/server/src/main/java/org/elasticsearch/index/shard/IndexShard.java Line 2308 in 733a6d3
|
@clandry94 @DaveCTurner these are internal refreshes. |
Just a quick update to this, I've finally gotten some time to work on collecting external refresh metrics and have something that I think is good. I'm planning on opening up a PR this coming week or next week. Sorry for the long delay 😄 |
Close in favor of #38643. |
Right now, the stats API only provides refresh metrics regarding internal refreshes. This isn't very useful and somewhat misleading for cluster administrators since the internal refreshes are not indicative of documents being available for search. In this PR I added a new metric for collecting external refreshes as they occur and exposing them through the stats API. Now, calling an endpoint for stats will yield external refresh metrics as well. Relates #36712
Right now, the stats API only provides refresh metrics regarding internal refreshes. This isn't very useful and somewhat misleading for cluster administrators since the internal refreshes are not indicative of documents being available for search. In this PR I added a new metric for collecting external refreshes as they occur and exposing them through the stats API. Now, calling an endpoint for stats will yield external refresh metrics as well. Relates elastic#36712
Right now, the stats API only provides refresh metrics regarding internal refreshes. This isn't very useful and somewhat misleading for cluster administrators since the internal refreshes are not indicative of documents being available for search. In this PR I added a new metric for collecting external refreshes as they occur and exposing them through the stats API. Now, calling an endpoint for stats will yield external refresh metrics as well. Relates #36712
Right now, the stats API only provides refresh metrics regarding internal refreshes. This isn't very useful and somewhat misleading for cluster administrators since the internal refreshes are not indicative of documents being available for search. In this PR I added a new metric for collecting external refreshes as they occur and exposing them through the stats API. Now, calling an endpoint for stats will yield external refresh metrics as well. Relates #36712
Describe the feature:
Currently, refresh stats are contained at the index level are an average of all shard refreshes within that index and exposed through the
_stats
api. Likewise, individual shards do collect refresh statistics, but only forINTERNAL
refresh events and these statistics are not publicly accessible through the rest API.I'm proposing the following two features to be added to elasticsearch:
EXTERNAL
andINTERNAL
refreshes within shards2) Extending thethis is already implemented e.g._stats
to provide shard level refresh statistics.would respond with
Related issue and prior discussion with @s1monw #36541
I can take on this and start working on it if all looks good 👍
The text was updated successfully, but these errors were encountered: