github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-04-24 23:27:25 -04:00
Code Issues Projects Releases Packages Wiki Activity

DOC CCR Disaster recovery does not handle Security configuration (#85522)

Browse source 
We do not support and don't plan to support disaster recovery arrangements
where Security configuration is replicated between the production and the
disaster recovery cluster because the cluster-local Security APIs assume
exclusive write on the .security system index.
This commit is contained in:
Albert Zaharovits 2022-10-12 13:53:53 +03:00 • committed by GitHub
parent fa37ea9161
commit 73cdc7b80a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/reference/ccr/index.asciidoc
View file

@ -54,6 +54,12 @@ https://www.elastic.co/webinars/replicate-elasticsearch-data-with-cross-cluster-
Then, <<ccr-getting-started-tutorial,set up {ccr}>> on your local machine and work Then, <<ccr-getting-started-tutorial,set up {ccr}>> on your local machine and work
through the demo from the webinar. through the demo from the webinar.
IMPORTANT: In all of these use cases, you must
<<manually-configure-security,configure security>> independently on every
cluster. The security configuration is not replicated when configuring {ccr} for
disaster recovery. To ensure that the {es} `security` feature state is backed up,
<<back-up-specific-feature-state,take snapshots>> regularly. You can then restore
the native users, roles, and tokens from your security configuration.
[discrete] [discrete]
[[ccr-disaster-recovery]] [[ccr-disaster-recovery]]
==== Disaster recovery and high availability ==== Disaster recovery and high availability
@ -193,7 +199,7 @@ follower shard pauses
==== Processing updates ==== Processing updates
You can't manually modify a follower index's mappings or aliases. To make You can't manually modify a follower index's mappings or aliases. To make
changes, you must update the leader index. Because they are read-only, follower changes, you must update the leader index. Because they are read-only, follower
indices reject writes in all configurations. indices reject writes in all configurations.
NOTE: Although changes to aliases on the leader index are replicated to follower NOTE: Although changes to aliases on the leader index are replicated to follower
indices, write indices are ignored. Follower indices can't accept direct writes, indices, write indices are ignored. Follower indices can't accept direct writes,