This wasn't clear from the documentation. Reported-by; Paul Greenberg <green...@outlook.com> Signed-off-by: Ben Pfaff <b...@ovn.org> --- Documentation/ref/ovsdb.7.rst | 3 +++ ovsdb/ovsdb-server.1.in | 3 +++ 2 files changed, 6 insertions(+)
diff --git a/Documentation/ref/ovsdb.7.rst b/Documentation/ref/ovsdb.7.rst index 39d85b6e5774..f891309fc05d 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 diff --git a/ovsdb/ovsdb-server.1.in b/ovsdb/ovsdb-server.1.in index 2d80dafffb7d..9f78e87f655c 100644 --- a/ovsdb/ovsdb-server.1.in +++ b/ovsdb/ovsdb-server.1.in @@ -339,6 +339,9 @@ executed. .IP Use \fBovsdb\-client wait\fR (see \fBovsdb\-client\fR(1)) to wait until the server has left the cluster. +.IP +Once a server leaves a cluster, it may never rejoin it. Instead, +create a new server and join it to the cluster. . .IP "\fBcluster/kick \fIdb server\fR" Start graceful removal of \fIserver\fR from \fIdb\fR's cluster, like -- 2.16.1 _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
