[KUDU-1580] Connection negotiation timeout to tablet server is treated as unretriable error on write operations

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.10.0
• Fix Version/s: 1.4.0
• Component/s: client
• Labels: client
• Target Version/s: 1.4.0
• Code Review: http://gerrit.cloudera.org:8080/6926
• Assignee: Alexey Serbin
• Reporter: Todd Lipcon
• Created: 27/Aug/16 00:36
• Updated: 26/Oct/22 10:51
• Resolved: 25/May/17 01:39

Description

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.

Issue Links

• is related to: KUDU-3414 Client tries with the same address over and over in case of negotiation timeout
• is related to: KUDU-1034 Client does not fail over due to timeout
• relates to: KUDU-2027 Connection negotiation timeout to tablet server is treated as unretriable error on scan operations
• relates to: KUDU-2021 Add an integration test: in case of multi-master, RPC is retried in case of negotiation error with master