hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14535) Unit test for rpc connection concurrency / deadlock testing
Date Tue, 06 Oct 2015 05:05:26 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944514#comment-14944514
] 

stack commented on HBASE-14535:
-------------------------------

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. The difference here is that it would be known
non-deterministic? How is distingushed from tests that are non-known-to-be-non-deterministic?

bq. Even if it fails 10-20%, we can find it useful

Trying to understand. So, before checkin, you can make it fail? If so, can we fix before commit?

> 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)

Mime
View raw message