You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/01 18:18:00 UTC

[jira] [Updated] (KUDU-1537) Exactly-once semantics for DDL operations

     [ https://issues.apache.org/jira/browse/KUDU-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grant Henke updated KUDU-1537:
------------------------------
    Labels: roadmap-candidate  (was: )

> Exactly-once semantics for DDL operations
> -----------------------------------------
>
>                 Key: KUDU-1537
>                 URL: https://issues.apache.org/jira/browse/KUDU-1537
>             Project: Kudu
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.9.1
>            Reporter: Adar Dembo
>            Priority: Major
>              Labels: roadmap-candidate
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)