Failback when clusterA comes back
editFailback when clusterA
comes back
edit-
You can simulate this by turning
cluster A
back on. -
Data ingested to
cluster B
duringcluster A
's downtime will be automatically replicated.-
data streams on cluster A
-
150 documents in
logs-generic-default-replicated_from_clusterb
-
50 documents in
logs-generic-default
-
150 documents in
-
data streams on cluster B
-
50 documents in
logs-generic-default-replicated_from_clustera
-
150 documents in
logs-generic-default
-
50 documents in
-
- If you have Logstash running at this time, you will also observe traffic is sent to both clusters.