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

[BUG] System Indices breaking cluster state invariance after upgrade from 2.15 #16643

Closed
shiv0408 opened this issue Nov 14, 2024 · 1 comment · Fixed by #16644
Closed

[BUG] System Indices breaking cluster state invariance after upgrade from 2.15 #16643

shiv0408 opened this issue Nov 14, 2024 · 1 comment · Fixed by #16644
Labels
bug Something isn't working Plugins

Comments

@shiv0408
Copy link
Member

Describe the bug

When we are upgraded our cluster from 2.15 to 2.17, we observed that multiple system indices were having different IndexMetadata on Cluster Manager node and remaining follower nodes. Where system flag is true on cluster manager but on followers it is false with same version.
This breaks the invariance guarantee of IndexMetadata being same as cluster manager on all nodes.
This has started happening because we have marked various index as system index as part of opensearch-project/security#4439

Related component

Plugins

To Reproduce

  1. Create a multinode 2.15 cluster with plugins such as observability, which create a system index.
  2. Upgrade the cluster to 2.16/2.17
  3. Active Cluster Manager have system flag true for .opensearch-observability index metadata, but all follower show false

Expected behavior

Cluster State Index Metadata should be same for all the nodes.

Additional Details

This is happening in both the causes, with remote_store.publication.enabled: true/false

@dblock
Copy link
Member

dblock commented Dec 2, 2024

[Catch All Triage - 1, 2, 3]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Plugins
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants