[
https://issues.apache.org/jira/browse/KUDU-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15440324#comment-15440324
]
Todd Lipcon commented on KUDU-1580:
-----------------------------------
This seems to be causing relatively high flakiness of raft_consensus-itest's
MultiThreadedInsertWithFailovers test case, unless I bump the rpc negotiation
timeout up. I'll apply that workaround temporarily and leave a pointer to this
JIRA.
> Connection negotiation timeout to tablet server is treated as unretriable
> error
> -------------------------------------------------------------------------------
>
> Key: KUDU-1580
> URL: https://issues.apache.org/jira/browse/KUDU-1580
> Project: Kudu
> Issue Type: Bug
> Components: client
> Affects Versions: 0.10.0
> Reporter: Todd Lipcon
>
> In the case that the leader tablet server is up but "frozen", the client will
> get a connection negotiation timeout trying to establish an RPC connection.
> It appears that this Status::TimeOut() is treated as a non-retriable error by
> WriteRpc::AnalyzeResponse, so the client gets a failure even if there has
> been a leader re-election within the client-provided deadline.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
