summaryrefslogtreecommitdiff
path: root/Documentation/ref
diff options
context:
space:
mode:
authorBen Pfaff <blp@ovn.org>2018-10-29 16:37:11 -0700
committerBen Pfaff <blp@ovn.org>2018-11-02 11:29:10 -0700
commit80c42f7f218fedd5841aa62d7e9774fc1f9e9b32 (patch)
tree3bd6616e02542797722c88f1d3fb64701891e55b /Documentation/ref
parentaf26093ab197c309dc0cfa83c5a2db34706f6021 (diff)
downloadopenvswitch-80c42f7f218fedd5841aa62d7e9774fc1f9e9b32.tar.gz
ovsdb: Clarify that a server that leaves a cluster may never rejoin.
This wasn't clear from the documentation. Reported-by; Paul Greenberg <greenpau@outlook.com> Reviewed-by: Yifeng Sun <pkusunyifeng@gmail.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
Diffstat (limited to 'Documentation/ref')
-rw-r--r--Documentation/ref/ovsdb.7.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/ref/ovsdb.7.rst b/Documentation/ref/ovsdb.7.rst
index 39d85b6e5..f891309fc 100644
--- a/Documentation/ref/ovsdb.7.rst
+++ b/Documentation/ref/ovsdb.7.rst
@@ -255,6 +255,9 @@ cluster: transactions not yet replicated to the server will be lost, and
transactions not yet applied to the cluster may be committed. Afterward, any
servers in its former cluster will regard the server to have failed.
+Once a server leaves a cluster, it may never rejoin it. Instead, create a new
+server and join it to the cluster.
+
The servers in a cluster synchronize data over a cluster management protocol
that is specific to Open vSwitch; it is not the same as the OVSDB protocol
specified in RFC 7047. For this purpose, a server in a cluster is tied to a