Bi-directional recovery: Failover when clusterA is down
Elastic Cloud Hosted lets you manage and configure one or more deployments of the versioned Elastic Stack, hosted on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
ECH
Generally available
ECK
Generally available
ECE
Generally available
Self-managed
Generally available
You can simulate this by shutting down either of the clusters. Let’s shut down
cluster Ain this tutorial.Start Logstash with the same configuration file. (This step is not required in real use cases where Logstash ingests continuously.)
Shell ### On Logstash server ### bin/logstash -f multiple_hosts.confObserve all Logstash traffic will be redirected to
cluster Bautomatically.TipYou should also redirect all search traffic to the
clusterBcluster during this time.The two data streams on
cluster Bnow 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
- 50 documents in
data streams On cluster B (up)
- 50 documents in
logs-generic-default-replicated_from_clustera - 150 documents in
logs-generic-default
- 50 documents in