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] Documentation for archived cluster and index settings. #4707

Open
1 of 4 tasks
ankitkala opened this issue Aug 7, 2023 · 1 comment
Open
1 of 4 tasks

[DOC] Documentation for archived cluster and index settings. #4707

ankitkala opened this issue Aug 7, 2023 · 1 comment
Assignees
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. Sev3 Medium priority. Content that's missing, driven by dev, PM or the community.

Comments

@ankitkala
Copy link
Member

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
Whenever OpenSearch stumbles upon a cluster/index setting which it doesn't recognize, it moves the setting to archived settings. Customer can't modify any other setting unless these archived settings are cleared up.

We don't have any documentation around this behaviour and how to remediate.

Archived cluster level settings can be cleared up by

PUT _cluster/settings
{
  "persistent": {
    "archived.*": null
  }
}

Removal for archived index setting doesn't work as of now(opensearch-project/OpenSearch#2803), we are introducing the fix here which allows users to clear the settings on closed indices.
To clear the archived setting on an index,

  1. Close the index.
  2. Clear the setting.
  3. Reopen the index.
POST /my-index/_close

PUT /my-index/_settings
{
  "archived.*": null
}

POST /my-index/_open

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

@Naarcha-AWS Naarcha-AWS added 1 - Backlog Issue: The issue is unassigned or assigned but not started Blocked PR: Cannot move forward without assistance Sev3 Medium priority. Content that's missing, driven by dev, PM or the community. and removed untriaged labels Aug 17, 2023
@hdhalter
Copy link
Contributor

Thanks for entering this issue, @ankitkala ! Can you please open a PR to update the documentation? Thank you.

@hdhalter hdhalter added 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. and removed 1 - Backlog Issue: The issue is unassigned or assigned but not started Blocked PR: Cannot move forward without assistance labels Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. Sev3 Medium priority. Content that's missing, driven by dev, PM or the community.
Projects
None yet
Development

No branches or pull requests

3 participants