OpenSearch for Jira early access program (EAP02)

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

The early access program (EAP) of OpenSearch for Jira gives you an opportunity to test apps' compatibility with OpenSearch.

On this page:

Configure Jira to use OpenSearch

As Jira instances grow in size and scale, the default search engine, Lucene, may be slower to index and return search results. To address this, Jira Data Center now offers an alternative search engine as an opt-in feature—OpenSearch. OpenSearch can take advantage of multi-node instances to manage process-intensive indexing. In the user interface, the search experience remains the same for users.

Explore how to configure OpenSearch for Jira

Implemented changes

We've implemented the following changes in the EAP02:

Known limitations

Check out current limitations and known issues with OpenSearch support in Jira 11 Early Access Program (EAP02). These limitations might affect your experience with searching, indexing, and overall performance:

If a plugin hasn’t been migrated to the search API, it won’t work with OpenSearch.


Workarounds

Unbounded queries

By default, OpenSearch limits search results to 10,000 hits. Many queries in Jira attempt to retrieve all available results. These queries may fail until we replace them with more efficient alternatives, such as aggregation or streaming.

In the meantime, you can increase the OpenSearch maximum result window setting:

{
  "index": {
    "max_result_window": "2147483647"
  }
}

More about the OpenSearch max_result_window setting.

Project re-index

Re-index the whole Jira instance instead of a single project.

Last modified on Sep 30, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.