Index consistency check fails on an empty index when using OpenSearch

XMLWordPrintable

    • Type: Bug
    • Resolution: Not a bug
    • Priority: Low
    • None
    • Affects Version/s: 11.2.0
    • Component/s: Indexing
    • None
    • 11.02
    • Severity 3 - Minor
    • Hide

      Fix is in progress and will be released with 11.2.1

      Show
      Fix is in progress and will be released with 11.2.1

      Issue Summary

      When migrating from Lucene to OpenSearch and starting a new node configured to use OpenSearch, the node will fail to start successfully i.e. it's /status endpoint will return a 500. This is due to the Index consistency check failing due to the default 10% fault tolerance.

      Steps to Reproduce

      1. Configure a new Jira node to use OpenSearch
      2. Start the node in an existing cluster (i.e. one which has many projects and issues)

      Expected Results

      The node starts up and can accept traffic

      Actual Results

      The node returns a 500 on the /status endpoint, preventing it from starting up successfully.

      The below INFO log entry is found in the atlassian-jira.log file:

      Index consistency check finished. indexConsistent: false; timeToCheckIndexConsistency:...
      

      Workaround

      Set -Dcom.atlassian.jira.index.consistency.tolerance.percentage=100 on the OpenSearch configured node and restart.

        1. image-20251111-071744.png
          126 kB
          Yifei Zhang
        2. image-20251111-040917.png
          125 kB
          Yifei Zhang

            Assignee:
            Yifei Zhang
            Reporter:
            Will Yasvoin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: