hbase-issues mailing list archives

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

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

Andrew Purtell commented on HBASE-14535:

If I parachuted in and found this test only failing in some cases but not in others, while
trying to clean up a slew of flakes, I'd likely disable this or move it out to an IT. True,
every failure should be looked at, but we let flakiness build up in our suite and leave it
to angels to come in later and triage. When triaging, deep analysis is deferred, by definition.

On the other hand, integration tests are expected to have some level of nondeterminism as
they are designed to run against a full cluster with a lot of moving parts. 

> 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

View raw message