This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
« Initial setup Failback when clusterA comes back »
Elastic Docs ›Elasticsearch Guide [master] ›Cross-cluster replication ›Tutorial: Disaster recovery based on bi-directional cross-cluster replication

Failover when clusterA is down

edit

Failover when clusterA is down

edit
  1. You can simulate this by shutting down either of the clusters. Let’s shut down cluster A in this tutorial.

  2. 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

  3. 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.

  4. 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
« Initial setup Failback when clusterA comes back »