Perform index checking in a caller thread #82249
Merged
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
Since 8.11 lucene performs index checking concurrently using disposable fixed thread pool executor by default. Setting thread count to 1 to keep prior behaviour (check is executed in single caller thread).
idegtiarenko
added
>test
|
Pinging @elastic/es-distributed (Team:Distributed) |
idegtiarenko
added a commit
to idegtiarenko/elasticsearch
that referenced
this pull request
Jan 5, 2022
Since 8.11 lucene performs index checking concurrently using disposable fixed thread pool executor by default. Setting thread count to 1 to keep prior behavior (check is executed in single caller thread).
💔 Backport failed
You can use sqren/backport to manually backport by running |
idegtiarenko
added a commit
to idegtiarenko/elasticsearch
that referenced
this pull request
Jan 5, 2022
Since 8.11 lucene performs index checking concurrently using disposable fixed thread pool executor by default. Setting thread count to 1 to keep prior behavior (check is executed in single caller thread).
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 5, 2022
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 5, 2022
astefan
pushed a commit
to astefan/elasticsearch
that referenced
this pull request
Jan 7, 2022
Since 8.11 lucene performs index checking concurrently using disposable fixed thread pool executor by default. Setting thread count to 1 to keep prior behavior (check is executed in single caller thread).
astefan
pushed a commit
to astefan/elasticsearch
that referenced
this pull request
Jan 7, 2022
Since 8.11 lucene performs index checking concurrently using disposable fixed thread pool executor by default. Setting thread count to 1 to keep prior behavior (check is executed in single caller thread).
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.
Since 8.11 lucene performs index checking concurrently
using disposable fixed thread pool executor by default.
Setting thread count to 1 to keep prior behavior
(check is executed in single caller thread).
Closes #81949