[KUDU-2046] Client should fail over timed out write operations

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.0
• Component/s: client
• Assignee: Unassigned
• Reporter: Todd Lipcon
• Created: 19/Jun/17 21:32
• Updated: 16/Feb/18 14:03

Description

This is similar to KUDU-1034, which was partially fixed in 4263b037844fca595a35f99479fbb5765ba7a443. That fix was partial in the following ways:

• it works when the client times out during negotiation, since the negotiation timeout is typically shorter than the total write operation timeout
• if the client has an already-estabished connection, the Write RPC is sent with a timeout equal to the entire user-specified timeout. So, if the server side is hung, then the client will fully time out the user operation and return an error before it tries any other replica. The fix for KUDU-1034 ensured that the server was marked down, thus fixing any future write attempt, but doesn't prevent the TimedOut error from bubbling up to the original caller.

Issue Links

• relates to: KUDU-1034 Client does not fail over due to timeout