Adar Dembo has posted comments on this change. Change subject: design-docs: multi-master for 1.0 release ......................................................................
Patch Set 2: (1 comment) http://gerrit.cloudera.org:8080/#/c/2527/2/docs/design-docs/multi-master-1.0.md File docs/design-docs/multi-master-1.0.md: Line 181: memory and ignores all requested actions from an older term. > Hmm, David and I talked about that, but we concluded that it was unnecessar FWIW, this is non-trivial to implement. Here are some things to consider: 1. We need to introduce a per-tserver ConsensusMetadata to track the state of the masters. 2. We need to add a ConsensusMetadataPB to every bit of master->tserver communication. We could make do with just the term, but reusing ConsensusMetadataPB may also help with making master Raft configuration changes at run time. 3. We need to add "dirtiness" to ConsensusMetadataPB so that a tserver can easily update/flush when servicing an RPC or heartbeat response. Perhaps I'm overthinking this; is there a simpler way to think about persisting the current term? -- To view, visit http://gerrit.cloudera.org:8080/2527 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: comment Gerrit-Change-Id: Iad76012977a45370b72a04d608371cecf90442ef Gerrit-PatchSet: 2 Gerrit-Project: kudu Gerrit-Branch: master Gerrit-Owner: Adar Dembo <[email protected]> Gerrit-Reviewer: Adar Dembo <[email protected]> Gerrit-Reviewer: Dan Burkert <[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
