Verifying Elasticsearch synchronization
Important
Elasticsearch is only supported up to version 6.8, which is no longer supported by Elastic. We therefore recommend using Storage as a Service instead, or if you do want to continue using self-hosted storage, using OpenSearch.
This procedure details how you can compare the data of two Elasticsearch clusters and confirm their synchronization. This setup is typically used when full geo-redundancy is required.
As various network- or database-related disruptions can lead to the clusters going out of sync, it is necessary to perform periodic manual checks to ensure the synchronization of both clusters. The primary objective is to ensure that both Elasticsearch clusters are at all times operational and supply the same data to the DMA if switching would be necessary.
Prerequisites
- Elasticsearch knowledge
- An element configured to use the Elasticsearch Cluster Monitor protocol
- A DataMiner Agent with access to http://[databaseIP]:9200
- A modern browser, e.g. Chrome, Edge, and Firefox
Procedure
Follow the procedure included in the documentation on configuring multiple Elasticsearch clusters.
Time estimate
| Item | Activity | Duration |
|---|---|---|
| 1 | Installing Elasticsearch Cluster Monitor protocol + creating element |
5 min. |
| 2 | Checking database health | 5 min. |
| 3 | Ensuring matching index names | 5 min. |
| 4 | Ensuring matching index sizes | 15 min. |