[
https://issues.apache.org/jira/browse/HBASE-14535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945401#comment-14945401
]
Enis Soztutar commented on HBASE-14535:
---------------------------------------
bq. I agree with Andrew (till I understand more). We've already got a fleet of
'non-deterministic' tests, so many, our CI runs are of no value
A non-deterministic test in this context is different from a flaky test. We
have a bunch of flaky tests that fail due to false negatives making jenkins
runs useless. This test in particular will not fail for false negatives, but it
might fail to catch deadlocks (false positive). If this test fails, I imagine
we take a look at it rather than classify as a flaky test.
> Unit test for rpc connection concurrency / deadlock testing
> ------------------------------------------------------------
>
> Key: HBASE-14535
> URL: https://issues.apache.org/jira/browse/HBASE-14535
> Project: HBase
> Issue Type: Sub-task
> Components: rpc
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 1.0.3, 1.1.3, 0.98.16
>
> Attachments: hbase-14535_v1.patch, hbase-14535_v2.patch
>
>
> As per parent jira and recent jiras HBASE-14449 + HBASE-14241 and
> HBASE-14313, we seem to be lacking some testing rpc connection concurrency
> issues in a UT env.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
