You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (JIRA)" <ji...@apache.org> on 2018/09/19 21:49:00 UTC
[jira] [Updated] (KUDU-2586) Refactor ConnectToClusterRpc to handle
FATAL_INVALID_AUTHENTICATION_TOKEN
[ https://issues.apache.org/jira/browse/KUDU-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Serbin updated KUDU-2586:
--------------------------------
Labels: client (was: )
> Refactor ConnectToClusterRpc to handle FATAL_INVALID_AUTHENTICATION_TOKEN
> -------------------------------------------------------------------------
>
> Key: KUDU-2586
> URL: https://issues.apache.org/jira/browse/KUDU-2586
> Project: Kudu
> Issue Type: Improvement
> Affects Versions: 1.8.0
> Reporter: Alexey Serbin
> Priority: Major
> Labels: client
>
> Current implementation of the {{ConnectToClusterRpc::SingleNodeCallback}} method does not handle {{FATAL_INVALID_AUTHENTICATION_TOKEN}} error code, relying on handling that in {{KuduClient::Data::SyncLeaderMasterRpc}}. As it turned out, that's not enough: see KUDU-2058.
> In short, current authn token should be removed from the messenger after upon receiving FATAL_INVALID_AUTHENTICATION_TOKEN error code in response from any master. A new token should be automatically acquired (if primary credentials are present) on next attempt to connect to the cluster.
> Also, it would be nice to refactor {{KuduClient::Data::SyncLeaderMasterRpc}} regarding handling of various error codes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)