Use default thread pools for Fleet Integration Knowledge system index #133265
Conversation
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
The Fleet Integration Knowledge index is a system index managed by Elasticsearch, but functionally it behaves like a regular search index. To align with this behavior, it should use the shared thread pools rather than the dedicated system thread pool. This ensures consistency with other search and ingest indices, while keeping the only distinction that it is managed internally by Elasticsearch.
jimczi
added
>non-issue
:Data Management/Indices APIs
elasticsearchmachine
added
Team:Data Management
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
dakrone
added
:Distributed Indexing/Distributed
elasticsearchmachine
added
the
Team:Distributed Indexing
Collaborator
|
Pinging @elastic/es-distributed-indexing (Team:Distributed Indexing) |
elasticsearchmachine
removed
the
Team:Data Management
Supplementing
approved these changes
Aug 20, 2025
Contributor
Supplementing
left a comment
Supplementing
left a comment
There was a problem hiding this comment.
LGTM from a Fleet standpoint!
pabloem
pushed a commit
to pabloem/elasticsearch
that referenced
this pull request
Aug 22, 2025
…elastic#133265) The Fleet Integration Knowledge index is a system index managed by Elasticsearch, but functionally it behaves like a regular search index. To align with this behavior, it should use the shared thread pools rather than the dedicated system thread pool. This ensures consistency with other search and ingest indices, while keeping the only distinction that it is managed internally by Elasticsearch.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
The Fleet Integration Knowledge index is a system index managed by Elasticsearch, but functionally it behaves like a regular search index. To align with this behavior, it should use the shared thread pools rather than the dedicated system thread pool. This ensures consistency with other search and ingest indices, while keeping the only distinction that it is managed internally by Elasticsearch.