hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10101) testOfflineRegionReAssginedAfterMasterRestart times out sometimes.
Date Mon, 09 Dec 2013 22:06:07 GMT

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

Jimmy Xiang commented on HBASE-10101:

[~jeffreyz], for patch v3-update, you clear the last assignment. However, the region could
have been open on the dead server for a while, so we need to wait till the current dead server
is done with log splitting to avoid possible data loss. For reset the meta location, the purpose
is the same, to make sure the right meta log is split.  As to the change in the master, originally,
it expires the sever if it is online; the change is to expire the server as long as it is
not known to be dead, i.e.,  it is online or unknown but not queued for SSH. For unknown,
as you said it could have not reported to the master.  But in this case, it is not going to
report to master any more, since verifymetalocation is already failed.

The test can be in TestAssignmentManagerOnCluster if the tests don't share the same cluster.
Since, the cluster is shared, if we restarts the cluster in the middle and the test fails,
other tests are impacted as well. TestMasterFailove seems to be a good place.

> testOfflineRegionReAssginedAfterMasterRestart times out sometimes.
> ------------------------------------------------------------------
>                 Key: HBASE-10101
>                 URL: https://issues.apache.org/jira/browse/HBASE-10101
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jimmy Xiang
>            Assignee: Jeffrey Zhong
>         Attachments: hbase-10101-v2.patch, hbase-10101-v3-update.patch, hbase-10101-v3.patch,
hbase-10101.patch, test.log, trunk-10101.patch, trunk-10101_v2.patch, trunk-10101_v3.patch
> 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

View raw message