Todd Lipcon has posted comments on this change. Change subject: docs: design for handling permanent master failures ......................................................................
Patch Set 4: (1 comment) http://gerrit.cloudera.org:8080/#/c/3393/4/docs/design-docs/master-perm-failure-1.0.md File docs/design-docs/master-perm-failure-1.0.md: PS4, Line 45: class of permanent failures I still think this is such a non-practical case that it's hardly worth mentioning. Even if your failure was bad RAM or something, are you really going to send someone to the datacenter to pull the disk out of the machine and attach it to a different machine so you can copy the data? Kind of unrealistic in an operational environment. I suppose the one case in which this would make sense is if your masters had mounted their data directory via a SAN or somesuch, so you could feasibly lose the machine and then mount the same LUN on a new box, but again it's rare enough in a typical Kudu environment that maybe this should be relegated to an appendix? -- To view, visit http://gerrit.cloudera.org:8080/3393 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: comment Gerrit-Change-Id: I2f05c319c89cf37e2d71fdc4b7ec951b2932a2b2 Gerrit-PatchSet: 4 Gerrit-Project: kudu Gerrit-Branch: master Gerrit-Owner: Adar Dembo <[email protected]> Gerrit-Reviewer: Adar Dembo <[email protected]> Gerrit-Reviewer: David Ribeiro Alves <[email protected]> Gerrit-Reviewer: Kudu Jenkins Gerrit-Reviewer: Mike Percy <[email protected]> Gerrit-Reviewer: Todd Lipcon <[email protected]> Gerrit-HasComments: Yes
