Switch built-in policies to max_primary_shard_size #69995
Merged
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
joegallo
added
:Data Management/ILM+SLM
Collaborator
|
Pinging @elastic/es-core-features (Team:Core/Features) |
joegallo
added a commit
that referenced
this pull request
Mar 4, 2021
This was referenced Mar 8, 2021
6 tasks
Contributor
Author
|
elastic/beats#25000 will switch elastic/beats over to |
Contributor
Author
|
logstash-plugins/logstash-output-elasticsearch#1008 covers switching logstash over. |
ph
added a commit
to elastic/beats
that referenced
this pull request
May 31, 2022
* Use max_primary_shard_size instead of max_size Based on change from elastic/elasticsearch#69995 Users are having a hard time to have the "right sized shards" (~50gb), but they also need to adjust the number of primaries to keep up with the ingest load. This doesn't well with the `max_size` option but it should work nicely with the newly introduced `max_primary_shard_size`. This change the default ILM policy shipped with beats. * Fix the test suite
chrisberkhout
pushed a commit
to elastic/beats
that referenced
this pull request
Jun 1, 2023
* Use max_primary_shard_size instead of max_size Based on change from elastic/elasticsearch#69995 Users are having a hard time to have the "right sized shards" (~50gb), but they also need to adjust the number of primaries to keep up with the ingest load. This doesn't well with the `max_size` option but it should work nicely with the newly introduced `max_primary_shard_size`. This change the default ILM policy shipped with beats. * Fix the test suite
This was referenced Sep 27, 2023
Closed
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.
Related to #63026
Also some changes to the docs so that
max_primary_shard_sizeis advertised a little more.