Disable circuit breaking for BigArrays #6381
Closed
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
The BigArrays limit is currently shared by the translog, netty, http and some queries/aggregations. If any of these consumers starts taking a lot of memory, then other ones might fail to allocate memory, which could have bad consequences, eg. if ping requests can't be sent. The plan is to come up with a better solution in 1.3. Close elastic#6332
This was referenced Jun 2, 2014
Closed
|
Is this a "don't upgrade to 1.20" kind of thing? |
|
LGTM @nik9000 we will likely do a bugfix release soonish so this can cause problems but the workaround is straight forward setting this to unlimited |
|
closing... |
clintongormley
changed the title
clintongormley
added
the
:Core/Infra/Circuit Breakers
clintongormley
changed the title
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.
The BigArrays limit is currently shared by the translog, netty, http and some
queries/aggregations. If any of these consumers starts taking a lot of memory,
then other ones might fail to allocate memory, which could have bad
consequences, eg. if ping requests can't be sent. The plan is to come up with
a better solution in 1.3.
Close #6332