-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Revert "Improving statsByShard performance when the number of shards is very large (#130857)" #137973
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
Revert "Improving statsByShard performance when the number of shards is very large (#130857)" #137973
Conversation
…is very large (elastic#130857)" This reverts commit 22c15bc.
|
Pinging @elastic/es-data-management (Team:Data Management) |
joegallo
left a comment
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.
I re-ran the steps that you would have run myself, and I ended up with zero diff compared to what you ended up with, so I'm ✅ once CI is.
e138f5f
into
elastic:patch/serverless-fix
…is very large (elastic#130857)" (elastic#137973) This reverts commit 22c15bc.
💔 Backport failed
You can use sqren/backport to manually backport by running |
…is very large (elastic#130857)" (elastic#137973) This reverts commit 22c15bc.
…is very large (elastic#130857)" (elastic#137973) This reverts commit 22c15bc.
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
…is very large (elastic#130857)" (elastic#137973) This reverts commit 22c15bc. (cherry picked from commit e138f5f) # Conflicts: # server/src/test/java/org/elasticsearch/indices/IndicesQueryCacheTests.java
… is very large (elastic#130857)" (elastic#137973) (elastic#137984) This reverts commit 391de08.
… is very large (elastic#130857)" (elastic#137973) (elastic#137984) This reverts commit 391de08.
Reverting #130857 due to unexpected performance regression.