› › ›

Failover when clusterA is down

You can simulate this by shutting down either of the clusters. Let’s shut down cluster A in this tutorial.
Start Logstash with the same configuration file. (This step is not required in real use cases where Logstash ingests continuously.)
```
### On Logstash server ###
bin/logstash -f multiple_hosts.conf
```
Observe all Logstash traffic will be redirected to cluster B automatically.

You should also redirect all search traffic to the clusterB cluster during this time.
The two data streams on cluster B now contain a different number of documents.
- data streams on cluster A (down)
  - 50 documents in logs-generic-default-replicated_from_clusterb
  - 50 documents in logs-generic-default
- data streams On cluster B (up)
  - 50 documents in logs-generic-default-replicated_from_clustera
  - 150 documents in logs-generic-default

© 2023-2025 Elasticsearch
As of September 2024, Elasticsearch is available under a choice of three licenses: the Server Side Public License (SSPL), the Elastic License, or the AGPLv3 (OSI approved).
Elasticsearch and the Elasticsearch logo are trademarks of Elasticsearch B.V., registered in the U.S. and in other countries.
https://www.elastic.co/guide/en/elasticsearch/reference/8.17/_failover_when_clustera_is_down_2.html