hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-8169) TestMasterFailover#testMasterFailoverWithMockedRITOnDeadRS may fail due to regions randomly assigned to a RS
Date Thu, 04 Apr 2013 23:34:17 GMT

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

Lars Hofhansl updated HBASE-8169:
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.95.1
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Committed to 0.94, 0.95, and 0.98.
Thanks for the patch Jeffrey.
                
> TestMasterFailover#testMasterFailoverWithMockedRITOnDeadRS may fail due to regions randomly
assigned to a RS
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8169
>                 URL: https://issues.apache.org/jira/browse/HBASE-8169
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.98.0, 0.94.7
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>            Priority: Minor
>             Fix For: 0.95.1, 0.98.0, 0.94.7
>
>         Attachments: hbase-8169_0.94_rebased.patch, hbase-8169.patch, hbase-8169_trunk.patch,
RegionAssignedRandomly.txt
>
>
> In the test case, we use "master.assignRegion(hri);" to assign regions to live RS or
dead RS(will be aborted during the test). While master.assignRegion may not always successfully
assign a region to the expected RS due to following error:
> 1) We firstly try to open a region in region server, let's say RS1
> 2) For some reason the region open takes more than a time out period
> 3) AM tries to reassign it and force a new plan due to the time out
> 4) the Region is re-assigned to a random RS 
> Then it cause the test case failure due to regions setup isn't in expected state.
> I attached a log with extra added logging info and some stack traces(with (new Exception()).printStackTrace()
so you can ignore java.lang.Exception). You can search region 36716be644bc9c78b3a96e0d4a43c183
to see master.assignRegion assigned a region to a randome RS. I saw the test failed once in
5 times in a loop.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message