[
https://issues.apache.org/jira/browse/KUDU-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032046#comment-17032046
]
ASF subversion and git services commented on KUDU-3042:
-------------------------------------------------------
Commit e97e8947f7edced314a9e22084a2738e8474451b in kudu's branch
refs/heads/master from Thomas Tauber-Marshall
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=e97e894 ]
[rpc-test] fix flaky TestCancellation
KUDU-3042 added a test case for the interaction between rpc
cancellation and rpc timeouts. This test was flaky as it assumed that
rpcs that are cancelled will return with an aborted status, which is
not always the case due to cancellation being best effort.
The fix is to make the test more permissive by allowing the rpcs to
fail with either an aborted or a timed out status.
Change-Id: If140a9215c94d781c2c61ec30b18d2d67d80310a
Reviewed-on: http://gerrit.cloudera.org:8080/15174
Tested-by: Kudu Jenkins
Reviewed-by: Adar Dembo <[email protected]>
> DCHECK hit in Connection::HandleOutboundCallTimeout
> ---------------------------------------------------
>
> Key: KUDU-3042
> URL: https://issues.apache.org/jira/browse/KUDU-3042
> Project: Kudu
> Issue Type: Bug
> Components: rpc
> Affects Versions: 1.12.0
> Reporter: Thomas Tauber-Marshall
> Priority: Critical
> Fix For: 1.12.0
>
>
> When testing a patch for IMPALA-8712, I ran into the error:
> {noformat}
> F0114 12:18:29.332731 22712 connection.cc:379] Check failed: car->call
> {noformat}
> This occurs when an async rpc is cancelled and then hits its timeout, as the
> timeout handling code assumes that the call is still valid.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
