Mike Percy has posted comments on this change. Change subject: docs: clarify steps for changing master from multi-master deployment ......................................................................
Patch Set 3: (1 comment) http://gerrit.cloudera.org:8080/#/c/8032/3/docs/administration.adoc File docs/administration.adoc: PS3, Line 399: * Establish a maintenance window (one hour should be sufficient). During this time the Kudu cluster : will be unavailable. > Original nodes A (dead), B*, C, and attempted to replace A with D. Tried go The problem is you only updated the config files on disk. You didn't add the configuration change to the WAL, and Raft replicates what's in the WAL. Come to think of it, it's quite dangerous to do it in a rolling fashion because the configuration is changing without updating the WAL and therefore 2 servers can have different configs but either one can get elected since they have the same last-logged opid in the WAL. In short, until we support config change on the master we should bring down all of the masters before modifying all of their configs and bringing them all back up. -- 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: 3 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-Reviewer: Mike Percy <mpe...@apache.org> Gerrit-HasComments: Yes
