Reduce multiple indices overhead, don't create Indices data on nodes that don't hold any shard for an index #441
Labels
Comments
|
Reduce multiple indices overhead, don't create Indices data on nodes that don't hold any shard for an index, closed by ae5bc20. |
medcl
pushed a commit
to medcl/elasticsearch
that referenced
this issue
Jul 1, 2011
…that don't hold any shard for an index, closes elastic#441.
williamrandolph
pushed a commit
to williamrandolph/elasticsearch
that referenced
this issue
Jun 4, 2020
Enhance value order when dealing with nested values relates elastic#441
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…equest elastic#441) MPC-4502: force imagePullPolicy to Always * force imagePullPolicy to Always Approved-by: Gideon Avida
costin
pushed a commit
to costin/elasticsearch
that referenced
this issue
Dec 19, 2022
🤖 ESQL: Merge upstream
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we remove all configuration options regarding segment memory charts as segment memory tracking will be removed in https://issues.apache.org/jira/browse/LUCENE-9387. Relates elastic#441
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
Fixes elastic#441 Fixes elastic#442
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Internal optimization. There is data associated with each index (parsed mappings, custom analyzers, and os on). Optimize to not create those index level structures if there is no shard of that index allocated on a node.
The text was updated successfully, but these errors were encountered: