Skip to content
Last update: June 10, 2024

Blue-Green Indexing


The blue-green indexing is supported by the ElasticSearch, ElasticSearch 8, and Azure Search modules.

Readmore Elastic Search module

Readmore Elastic Search 8 module

Readmore Azure Search module

After you choose Delete and build when building search index:

  1. A new backup index is generated for the chosen document type.
  2. The indexing operations are carried out on this backup index.
  3. Throughout the full indexing process, the existing index remains unaffected, allowing uninterrupted search operations.
  4. Once the reindexing is complete, a swap occurs: the backup index becomes active, while the previous index transitions to a backup role.

To revert to the previous index, use the Swap indices feature:

  1. Click Show backup indices in the top toolbar.

    Backup indices

  2. Click on the three dots to the left of the required document type.

  3. Select Swap indices in the popup menu.
  4. Click Hide backup indices in the top toolbar.

    Three dots

The roles of the backup and active indices have been exchanged.

Implementation Details

Elasticsearch implements blue-green indexing using Elasticsearch aliases. Search provider implementations use two aliases to distinguish one index role from the other: active and backup. The full index alias is built as scope name + document type name + alias name; for example, an active index alias for the Members index using the default scope will be default-member-active.

Each time you start the Delete and build process, the Elasticsearch index provider looks for an existing backup index by the backup alias, for example, default-member-backup, and deletes it if it is found. After that, when the reidnexing process starts, a new backup index is created with the `backup' alias. However, an actual index name is created dynamically: this is a special alphanumeric token suffix added to the end of the index name. The only way to tell which index is active is to look at its alias. After the indexing process is complete, the active and backup indices swap aliases, i.e. the active index becomes the backup index, and vice versa.

Kibana index alias