[
https://issues.apache.org/jira/browse/KUDU-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-2046:
------------------------------
Target Version/s: (was: 1.5.0)
> Client should fail over timed out write operations
> --------------------------------------------------
>
> Key: KUDU-2046
> URL: https://issues.apache.org/jira/browse/KUDU-2046
> Project: Kudu
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.0
> Reporter: Todd Lipcon
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
