OpenSearch 1.1.0 is here!

Tue, Oct 05, 2021 · Andrew Hopp, Charlotte Henkle, Eli Fisher, Kyle Davis

We are excited to announce the 1.1.0 release of OpenSearch, OpenSearch Dashboards, and the OpenSearch Project plugins (available to download today).

What’s Included in OpenSearch 1.1.0?

This release includes dozens of new features and hundreds of improvements (release notes), and we wanted to highlight some of the most exciting new features in this release:

  • Cross-Cluster Replication (CCR): With this feature, you will be able to deploy OpenSearch clusters across different servers, data centers, or even regions and setup a more fault-tolerant configuration. CCR provides low latency replication for indices with sequential consistency.
  • Lucene 8.9 Upgrade: Lucene 8.9 includes sorting improvements when building BKD indexes that can boost index building by 35x and speed up merging sorted fields and term vectors for smaller segments. It also includes a fix for a performance regression in boolean queries that was introduced in 8.8. Full details are available in the Lucene 8.9 change log.
  • CLI OpenSearch Upgrade Tool: While upgrading to OpenSearch from a compatible version of Elasticsearch, there are some manual tasks that need to be performed. The opensearch-upgrade tool included in the distribution automates those tasks by importing the existing configurations and applying them to the new installation of OpenSearch. For more information see the readme.
  • Anomaly Detection Upgrades: OpenSearch now has a unified workflow for realtime and historical anomaly detection within the same detector. You can now click through a single workflow to perform all of the necessary steps to create and run anomaly detection jobs. Anomaly Detection has also been upgraded to use an updated Random Cut Forest (RCF) algorithm and saw improvements to high cardinality anomaly detection.
  • Bucket Level Alerting: With Bucket Level Alerting, you can configure alerting policies that evaluate against aggregations grouped by a unique field value. For example, if you have an index that is ingesting health logs a number of different hosts, with Bucket Level Alerting, you could configure a monitor to alert when any host has a metric, like CPU or memory, that exceeds a defined threshold.

What’s next?

With the launch of 1.1.0, OpenSearch is already racing forward. There are a number of upcoming feature and enhancements including:

  • A shard level back pressure framework is being added to improve OpenSearch indexing reliability.
  • A number of new observability features are being added to help you analyze trace and log data.
  • OpenSearch’s k-NN plugin will add support for the updated FAISS algorithm that improves performance.
  • Anomaly detection will add visibility to which signals contributed to specific anomalies.

See additional active features on the project roadmap.

How can you contribute?

The OpenSearch community continues to grow and we invite new users and members to contribute! For almost any type of contribution, the first step is opening an issue (OpenSearch, OpenSearch Dashboards). Even if you think you already know what the solution is, writing down a description of the problem you’re trying to solve will help everyone get context when they review your pull request. If it’s truly a trivial change (e.g. spelling error), you can skip this step – but when in doubt, open an issue. If you’re excited to jump in, check out the “help wanted” tag in issues.

Do you have questions or feedback?

If you’re interested in learning more, have a specific question, or just want to provide feedback and thoughts, please visit (, open an issue on GitHub, or post in the forums. There are also regular Community Meetings that include progress updates at every session and include time for Q&A.

Thank you!

We knew OpenSearch would need to build a great open source community to succeed and we’re so excited about the progress! Not only is OpenSearch seeing some awesome contributions across the project but the community partners continue to grow (5 more partners have joined since 1.0.0). As always, everyone should be incredibly proud of the accomplishment of reaching 1.1.0 together.

Thank you for your continued support.