David Ribeiro Alves has posted comments on this change. Change subject: WIP: catalog manager audit/analysis ......................................................................
Patch Set 1: (5 comments) http://gerrit.cloudera.org:8080/#/c/2583/1/docs/design-docs/multi-master-1.0-supplement.md File docs/design-docs/multi-master-1.0-supplement.md: Line 3: UNKNOWN What is this state transition? do we store, or do something about UNKNOWN Line 4: 2. create tablets in state UNKNOWN, begin mutation to state PREPARING same question Line 5: 4. update in-memory maps (table by id/name, tablet by id) Hum this answers my question but, why is this useful? Line 18: - The two replications can be safely combined So can you combine them to see what they would look like? Or are you trying to lay out the current sequence before you lay out the new one? Maybe do a before/after. Would something like this make sense: - Create table in state RUNNING - Create tablets in state PREPARING - Write all to the master tablet - Update in-mem state accordingly - Reply to client - Send the create tablet RPCs (with embedded exactly once semantics) Line 27: a. create tablet t_new in state UNKNOWN, begin mutation to state PREPARING in general what is this "begin mutation"? -- To view, visit http://gerrit.cloudera.org:8080/2583 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ia3dd75552400b89718a0f789e96895a64d1fb91b Gerrit-PatchSet: 1 Gerrit-Project: kudu Gerrit-Branch: master Gerrit-Owner: Adar Dembo <[email protected]> Gerrit-Reviewer: David Ribeiro Alves <[email protected]> Gerrit-Reviewer: Kudu Jenkins Gerrit-Reviewer: Todd Lipcon <[email protected]> Gerrit-HasComments: Yes
