Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOC] Document behavior of new index.merge.policy setting #5119

Closed
rishabhmaurya opened this issue Sep 26, 2023 · 2 comments · Fixed by #5137
Closed

[DOC] Document behavior of new index.merge.policy setting #5119

rishabhmaurya opened this issue Sep 26, 2023 · 2 comments · Fixed by #5137
Assignees
Labels
3 - Done Issue is done/complete v2.11.0
Milestone

Comments

@rishabhmaurya
Copy link
Contributor

rishabhmaurya commented Sep 26, 2023

Is your feature request related to a problem? Please describe.
Yes. A new index setting (index.merge.policy) is introduced to configure the index merge policy (tiered and log_byte_size) for individual index. Also, a new cluster setting (indices.time_series_index.default_index_merge_policy) is introduced to set the default merge policy for index containing @timestamp field. Both the settings defaults are currently set as tiered.
Both settings are static.

Related to - opensearch-project/OpenSearch#9992

Describe the solution you'd like
Document this behavior here - https://opensearch.org/docs/latest/im-plugin/index-settings/ for index setting
and here for cluster setting - https://opensearch.org/docs/latest/api-reference/cluster-api/cluster-settings/

Describe alternatives you've considered
None

Additional context
Add any other context or screenshots about the feature request here.

@reta
Copy link
Contributor

reta commented Oct 3, 2023

FYI, this is scheduled for 2.11, thank you.

@hdhalter hdhalter added this to the v2.11 milestone Oct 3, 2023
@hdhalter hdhalter added v2.11.0 1 - Backlog Issue: The issue is unassigned or assigned but not started and removed enhancement New feature or request untriaged labels Oct 3, 2023
@rishabhmaurya
Copy link
Contributor Author

rishabhmaurya commented Oct 3, 2023

PR - #5137

I'm planning to write a blog post with more details once these concerns are addressed

@Naarcha-AWS Naarcha-AWS added 2 - In progress Issue/PR: The issue or PR is in progress. and removed 1 - Backlog Issue: The issue is unassigned or assigned but not started labels Oct 3, 2023
@hdhalter hdhalter added 3 - Done Issue is done/complete and removed 2 - In progress Issue/PR: The issue or PR is in progress. labels Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - Done Issue is done/complete v2.11.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants