Plugins endpoint#2830
Closed
q42jaap wants to merge 9 commits intoelastic:masterfrom
q42jaap:plugins-endpoint
Closed
Plugins endpoint#2830q42jaap wants to merge 9 commits intoelastic:masterfrom q42jaap:plugins-endpoint
q42jaap wants to merge 9 commits intoelastic:masterfrom
q42jaap:plugins-endpoint
Conversation
…non-fs directories If we cannot determine available space the fallback scenario is now to use random distribution instead of always using the last directory. Fixes #2820
breskeby
pushed a commit
to breskeby/elasticsearch
that referenced
this pull request
Feb 11, 2026
* Fast refresh indices should use RCO Depends on core ES PR elastic#113478 . Fast refresh indices should now use search shards, by using the new Refresh Cost Optimizations to refresh them. That means they can now start using search shards for gets/searches as well. The only difference now for fast refresh indices vs non fast refresh indices, is that the former have a lower min & default refresh interval (1s vs 5s) & are excluded from refresh throttling. Note that for BWC, we expect search shards to be upgraded first, before indexing shards. Until the cluster is fully upgraded, the promotable shards (whether upgraded or not) will still receive and execute gets/searches locally. An upgraded indexing node will refresh unpromotables (which must be upgraded search nodes). With the later , we will re-add checks that indexing shards should not receive a get/search. Closes Closes * Disable flush throttler for the upgrade test * PR comments --------- Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co>
breskeby
pushed a commit
to breskeby/elasticsearch
that referenced
this pull request
Feb 11, 2026
* Fast refresh indices to use search shards The changes of PR elastic#2830 were reverted because it induced . Now that the ticket is done, this PR re-introduces the reverted changes. Depends on core ES PR. Fast refresh indices should now use search shards, by using the new Refresh Cost Optimizations to refresh them. That means they can now start using search shards for gets/searches as well. The only difference now for fast refresh indices vs non fast refresh indices, is that the former have a lower min & default refresh interval (1s vs 5s) & are excluded from refresh throttling. Note that for BWC, we expect search shards to be upgraded first, before indexing shards. Until the cluster is fully upgraded, the promotable shards (whether upgraded or not) will still receive and execute gets/searches locally. An upgraded indexing node will refresh unpromotables (which must be upgraded search nodes). With the later , we will re-add checks that indexing shards should not receive a get/search. Closes * Submodule * Submodule * Merge upstream and update elasticsearch submodule to 673b24f --------- Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co>
breskeby
pushed a commit
to breskeby/elasticsearch
that referenced
this pull request
Feb 11, 2026
* Fast refresh indices should use RCO Depends on core ES PR elastic#113478 . Fast refresh indices should now use search shards, by using the new Refresh Cost Optimizations to refresh them. That means they can now start using search shards for gets/searches as well. The only difference now for fast refresh indices vs non fast refresh indices, is that the former have a lower min & default refresh interval (1s vs 5s) & are excluded from refresh throttling. Note that for BWC, we expect search shards to be upgraded first, before indexing shards. Until the cluster is fully upgraded, the promotable shards (whether upgraded or not) will still receive and execute gets/searches locally. An upgraded indexing node will refresh unpromotables (which must be upgraded search nodes). With the later , we will re-add checks that indexing shards should not receive a get/search. Closes Closes * Disable flush throttler for the upgrade test * PR comments --------- Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co>
breskeby
pushed a commit
to breskeby/elasticsearch
that referenced
this pull request
Feb 11, 2026
* Fast refresh indices to use search shards The changes of PR elastic#2830 were reverted because it induced . Now that the ticket is done, this PR re-introduces the reverted changes. Depends on core ES PR. Fast refresh indices should now use search shards, by using the new Refresh Cost Optimizations to refresh them. That means they can now start using search shards for gets/searches as well. The only difference now for fast refresh indices vs non fast refresh indices, is that the former have a lower min & default refresh interval (1s vs 5s) & are excluded from refresh throttling. Note that for BWC, we expect search shards to be upgraded first, before indexing shards. Until the cluster is fully upgraded, the promotable shards (whether upgraded or not) will still receive and execute gets/searches locally. An upgraded indexing node will refresh unpromotables (which must be upgraded search nodes). With the later , we will re-add checks that indexing shards should not receive a get/search. Closes * Submodule * Submodule * Merge upstream and update elasticsearch submodule to 673b24f --------- Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
I saw a TODO in HttpServer, /_plugin/ now works, it lists the names of the plugins. I couldn't find how to list the installed sites though.