[
https://issues.apache.org/jira/browse/KUDU-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18100501#comment-18100501
]
Paul Brannan commented on KUDU-3022:
------------------------------------
We have run into this issue in our system. As a workaround, if we get
ServiceUnavailable with status string that ends with "is already reserved",
then we try again until we get AlreadyPresent or time out.
We have not seen `ServiceUnavailable` when altering a table. We mostly use
KuduTableAlterer to add a new range partition, not to add columns or make other
changes. We have hit a race condition when multiple clients simultaneously
attempt to add a range partition (see KUDU-3794).
> C++ Client does not retry CreateTable on "new table name is already reserved"
> error
> -----------------------------------------------------------------------------------
>
> Key: KUDU-3022
> URL: https://issues.apache.org/jira/browse/KUDU-3022
> Project: Kudu
> Issue Type: Bug
> Components: client, master
> Reporter: Todd Lipcon
> Priority: Minor
>
> If two callers try to create a table with the same name at the same time, one
> of them can fail with the error: "new table name foo is already reserved".
> The comments in catalog_manager.cc seem to indicate that this should trigger
> the client to retry, but it seems the retry is not taking place.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
