[KUDU-1537] Exactly-once semantics for DDL operations

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.9.1
• Component/s: master
• Labels: roadmap-candidate
• Target Version/s: Backlog
• Assignee: Unassigned
• Reporter: Adar Dembo
• Created: 20/Jul/16 01:34
• Updated: 01/Jun/20 18:17

Description

Now that Kudu has a replay cache, we should use it for master DDL operations like CreateTable(), AlterTable(), and DeleteTable(). To do this we'll need to add some client-specific RPC state into the write that the leader master replicates to its followers, and use that state when an RPC is retried.

Some tests (e.g. master-stress-test) have workarounds that should be removed when this bug is fixed.

Issue Links

• depends upon: KUDU-568 Exactly-once semantics on writes