This is an automated email from the ASF dual-hosted git repository.
awong pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git
The following commit(s) were added to refs/heads/master by this push:
new 0335f3e [docs] add blurb about automatic master addition
0335f3e is described below
commit 0335f3ea6356011ac88c25a9a353b4fbec952a42
Author: Andrew Wong <[email protected]>
AuthorDate: Fri Feb 25 13:54:37 2022 -0800
[docs] add blurb about automatic master addition
The steps are updated in the latest version of Kudu, and this patch adds
a note indicating to readers that they do not need to go through the
administrative docs.
Change-Id: I15ada3ce0a4319a1e1b5340bdfb7a261ef260f8d
Reviewed-on: http://gerrit.cloudera.org:8080/18278
Tested-by: Kudu Jenkins
Reviewed-by: Attila Bukor <[email protected]>
---
docs/administration.adoc | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/docs/administration.adoc b/docs/administration.adoc
index 113c1c3..2ba1525 100644
--- a/docs/administration.adoc
+++ b/docs/administration.adoc
@@ -521,6 +521,13 @@ or because Kudu multi-master support was still
experimental at the time. This wo
how to migrate to a multi-master configuration. It can also be used to migrate
from two masters to
three, with straightforward modifications. Note that the number of masters
must be odd.
+NOTE: From Kudu version 1.16.0 onwards, new Kudu Masters automatically attempt
to contact other
+masters, determine whether a quorum has already been established, and if so,
attempt to join the
+quorum. The below steps do not need to be performed in these versions.
+
+NOTE: From Kudu version 1.15.0 onwards, the `kudu master add` command has been
added that simplifies
+the orchestration to migrate an existing Kudu cluster to multiple masters.
+
WARNING: The workflow is unsafe for adding new masters to an existing
configuration that already has
three or more masters. Do not use it for that purpose.
@@ -534,9 +541,6 @@ WARNING: The workflow presupposes at least basic
familiarity with Kudu configura
using vendor-specific tools the workflow also presupposes familiarity with
it and the vendor's instructions should be used instead as details may differ.
-NOTE: From Kudu version 1.15.0, a new `kudu master add` command has been added
that
-simplifies the orchestration to migrate an existing Kudu cluster to multiple
masters.
-
==== Prepare for the migration
. Establish a maintenance window (one hour should be sufficient). During this
time the Kudu cluster
