You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/09/08 19:13:46 UTC

[jira] [Resolved] (HBASE-6636) [0.92 UNIT TESTS] TestMasterZKSessionRecovery.testRegionAssignmentAfterMasterRecoveryDueToZKExpiry failed in 0.92 #513 and #496

     [ https://issues.apache.org/jira/browse/HBASE-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-6636.
--------------------------
    Resolution: Won't Fix

Old issue for old version. Resolving.

> [0.92 UNIT TESTS] TestMasterZKSessionRecovery.testRegionAssignmentAfterMasterRecoveryDueToZKExpiry failed in 0.92 #513 and #496
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-6636
>                 URL: https://issues.apache.org/jira/browse/HBASE-6636
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.1
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>
> The test class TestMasterZKSessionRecovery has been removed in trunk.  Its master tests were moved elsewhere or removed because useless (See nkeywal reasoning over in HBASE-5572 "KeeperException.SessionExpiredException management could be improved in Master"; it was actually removed by HBASE-5549 "Master can fail if ZooKeeper session expires").
> TestMasterZKSessionRecovery in 0.92 and 0.94 has an extra test that was not in trunk, the sporadically failing testRegionAssignmentAfterMasterRecoveryDueToZKExpiry.  This was added by "HBASE-6046
> Master retry on ZK session expiry causes inconsistent region assignments".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)