[
https://issues.apache.org/jira/browse/HBASE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842165#comment-13842165
]
Jeffrey Zhong commented on HBASE-10101:
---------------------------------------
The test case did uncover a race condition which should pre-exists. Basically
it relies on the old source server to be processed by SSH firstly otherwise you
can see that even the region assignment(second one) triggered by SSH is also
skipped. SSH region assignment should not be skipped at all. The issue should
happen for RITs in failed open state before. Below are related log lines:
{code}
2013-12-06 20:47:45,903 INFO [AM.-pool62-t1] master.AssignmentManager(1764):
Skip assigning
testOfflineRegionReAssginedAfterMasterRestart,I,1386391663080.be7906f27d850789818867916aa08c93.,
it is on a dead but not processed yet server
...
2013-12-06 20:47:45,926 INFO
[localhost.localdomain,59276,1386391665426-GeneralBulkAssigner-2]
master.AssignmentManager(1447): Skip assigning
testOfflineRegionReAssginedAfterMasterRestart,I,1386391663080.be7906f27d850789818867916aa08c93.,
it's host localhost.localdomain,47661,1386391655958 is dead but not
processed yet
{code}
> testOfflineRegionReAssginedAfterMasterRestart times out sometimes.
> ------------------------------------------------------------------
>
> Key: HBASE-10101
> URL: https://issues.apache.org/jira/browse/HBASE-10101
> Project: HBase
> Issue Type: Test
> Reporter: Jimmy Xiang
> Priority: Minor
> Attachments: hbase-10101.patch, test.log
>
>
> Sometimes, I got this test timed out. The log is attached. It could be
> because the new cluster takes a while to process the dead server, or assign
> meta.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
