Cherry-pick #11676 to 7.0: check for a valid limit before we process a memory event #11726
Conversation
This file contains 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
jsoriano
approved these changes
Apr 10, 2019
…elastic#11676) * check for a valid limit before we process a memory event (cherry picked from commit 97aec9b)
fearful-symmetry
force-pushed
the
backport_11676_7.0
branch
from
345d555 to
ad01193
Compare
|
did a rebase to make sure we're still good. |
kaiyan-sheng
approved these changes
Apr 15, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A backport of #11676. @ruflin Asked me to backport this, with the idea that the 7.0 branch will become 7.0.1, and it should not be merged until 7.0 is released.