From 053810b0b6fb0a27696fc58863969eb8ea2638ab Mon Sep 17 00:00:00 2001 From: Raoof Mohammed Date: Wed, 20 Jun 2018 11:26:10 -0400 Subject: [PATCH] docs: mirror_maker, rm readOnly, add uni-directional MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit mirror_maker doc mentioned "Data under the destination cluster’s mirroring prefix should be treated as read only." To avoid confusion, read only is being removed and a clear statement mentions that the updated values at destination wont be replicated from destination to origin. wont -> won't --- etcdctl/doc/mirror_maker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/etcdctl/doc/mirror_maker.md b/etcdctl/doc/mirror_maker.md index 6b14a2564d8..3da15dca88c 100644 --- a/etcdctl/doc/mirror_maker.md +++ b/etcdctl/doc/mirror_maker.md @@ -4,7 +4,7 @@ Mirror maker mirrors a prefix in the key-value space of an etcd cluster into ano If the mirror maker fails to connect to one of the clusters, the mirroring will pause. Mirroring can be resumed automatically once connectivity is reestablished. -The mirroring mechanism is unidirectional. Data under the destination cluster’s mirroring prefix should be treated as read only. The mirror maker only mirrors key-value pairs; metadata, such as version number or modification revision, is discarded. However, mirror maker still attempts to preserve update ordering during normal operation, but there is no ordering guarantee during initial sync nor during failure recovery following network interruption. As a rule of thumb, the ordering of the updates on the mirror should not be considered reliable. +The mirroring mechanism is unidirectional. Changing the value on the mirrored cluster won't reflect the value back to the origin cluster. The mirror maker only mirrors key-value pairs; metadata, such as version number or modification revision, is discarded. However, mirror maker still attempts to preserve update ordering during normal operation, but there is no ordering guarantee during initial sync nor during failure recovery following network interruption. As a rule of thumb, the ordering of the updates on the mirror should not be considered reliable. ``` +-------------+