Skip to content

[BUG] Indices do not pass initializiation in v3.3.0 #1522

@cinhtau

Description

@cinhtau

What is the bug?

ISM fails to initialize new indices after upgrading from v3.2.0 to v3.3.0
New created indices not managed by ISM, despite having a policy

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. Use OpenSearch v3.2.0
  2. Create index and add some docs, add to index policy with rollover_alias
  3. In-place upgrade OpenSearch v3.3.0
  4. Rollover manually
  5. Wait for index initialization
  6. No errors nor initialization

Reproduced on 1 clusters

  • Production Cluster with 24 nodes
  • Single Node Monitoring Cluster - works
  • Replication type: DOCUMENT

What is the expected behavior?

  • Successful initialization with State, Action and Info
  • After init, proceed to new states, e.g. rollover, allocation, etc

What is your host/environment?

  • OS: RHEL-8 8.10
  • Version: 3.3.0
  • Plugins: ISM

Do you have any screenshots?

Image

Do you have any additional context?

Could it be related with the timestamp problem? See opensearch-project/OpenSearch#19646

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions