Adar Dembo has posted comments on this change. Change subject: docs: clarify steps for removing master from multi-master deployment ......................................................................
Patch Set 1: (4 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 masters should be odd. Also, since this workflow brings down all the cluster, add a step about establishing a maintenance window (see above). Also, certain kinds of changes (i.e. dropping to a number of masters below the number of masters currently needed for a Raft majority) can incur data loss. We should find some way to incorporate that as a warning. PS1, Line 376: a that a Line 383: . Rewrite the Raft configuration on the remaining masters to remove the unwanted masters. See Step Let's be a little more explicit and say that in order to remove the unwanted masters, you rewrite the raft config to include just the remaining masters. Line 385: We should add a step to blow away the data/WAL directories of the unwanted masters, to prevent them from coming back to life and interfering with the new Raft configuration. -- 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: 1 Gerrit-Project: kudu Gerrit-Branch: master Gerrit-Owner: Andrew Wong <aw...@cloudera.com> Gerrit-Reviewer: Adar Dembo <a...@cloudera.com> Gerrit-Reviewer: Kudu Jenkins Gerrit-HasComments: Yes
