Remove "Push back excessive requests for stats (#83832)"#87054
Merged
joegallo merged 1 commit intoelastic:masterfrom May 23, 2022
Merged
Remove "Push back excessive requests for stats (#83832)"#87054joegallo merged 1 commit intoelastic:masterfrom
joegallo merged 1 commit intoelastic:masterfrom
Conversation
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
dakrone
approved these changes
May 23, 2022
Member
dakrone
left a comment
There was a problem hiding this comment.
LGTM if CI is happy, since I assume this is a straightforward revert?
Contributor
Author
Indeed -- there were two very minor conflicts due to changes in the surrounding context, nothing fancy. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #77466
This is a continuation of #85504. We don't want to ship #83832 (stats request rate limiting) with 8.3, because that rate limiting ends up causing problems for ILM with many indices (#85333). For the time being, we're going to revert #83832 from master (via this PR), so that we can re-approach #51992 with #85333 in mind.