[
https://issues.apache.org/jira/browse/KUDU-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997642#comment-16997642
]
Adar Dembo commented on KUDU-3022:
----------------------------------
This is also an issue for altering a table.
LookupRpc::SendRpcCb has the following code; maybe it needs to be pushed into
AsyncLeaderMasterRpc::RetryOrReconnectIfNecessary?
{noformat}
// Check for more application errors.
// Note: RetryOrReconnectIfNecessary only checked for generic application
// errors. This check is specific to LookupRpc.
if (new_status.ok() && resp_.has_error()) {
new_status = StatusFromPB(resp_.error().status());
if (new_status.IsServiceUnavailable()) {
// One or more of the tablets is not running. Retry after some time.
mutable_retrier()->DelayedRetry(this, new_status);
ignore_result(delete_me.release());
return;
}
}
{noformat}
> 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.3.4#803005)
