limit search thread pool size #5304
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
PSeitz
changed the title
|
I suggest closing this PR as we are not reproducing the health checks issue with heavy CPU queries |
|
Yes, I'll move the logging improvements to a new PR |
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.
Don't take all threads for search, reserve one thread for incoming requests. Otherwise there may not be enough CPU left to answer health checks
This behavior can be overruled by manually setting the search thread pool size via
QW_SEARCH_THREAD_POOL_SIZE.improve logging:
log actual indices that are being queried on leaf nodes instead of the patterns from the user request
reduce env var spam
Related to #5305