Andrew Wong has posted comments on this change. Change subject: docs: clarify steps for removing master from multi-master deployment ......................................................................
Patch Set 2: (6 comments) http://gerrit.cloudera.org:8080/#/c/8032/1/docs/administration.adoc File docs/administration.adoc: Line 374: ==== Removing masters from a Multi-Master Deployment > You should incorporate the warning from earlier about how the number of mas Done. I left the warning nearly verbatim, do you think that's fine? Or is there a more actionable warning (e.g. run `ksck` and copy over the raft config from the most up-to-date master) that would be more fitting? PS1, Line 376: has > nit: 'had' or just drop? I think "been" is fine here; I'm using it here as a verb, as in: "in the event that a multi-master deployment has been configured with too many nodes" PS1, Line 376: t > that a Done PS1, Line 381: > Is it worth adding a notion on disabling the kudu-master services for the m Done. Line 383: majority can incur data loss. > Let's be a little more explicit and say that in order to remove the unwante Done Line 385: . Establish a maintenance window (one hour should be sufficient). During this time the Kudu cluster > We should add a step to blow away the data/WAL directories of the unwanted Done -- To view, visit http://gerrit.cloudera.org:8080/8032 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: comment Gerrit-Change-Id: I4196dbb2f8a185e868a6906c7cf917d79c404c0d Gerrit-PatchSet: 2 Gerrit-Project: kudu Gerrit-Branch: master Gerrit-Owner: Andrew Wong <aw...@cloudera.com> Gerrit-Reviewer: Adar Dembo <a...@cloudera.com> Gerrit-Reviewer: Alexey Serbin <aser...@cloudera.com> Gerrit-Reviewer: Andrew Wong <aw...@cloudera.com> Gerrit-Reviewer: Kudu Jenkins Gerrit-HasComments: Yes
