[
https://issues.apache.org/jira/browse/HBASE-6881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465784#comment-13465784
]
Jimmy Xiang commented on HBASE-6881:
------------------------------------
Patch 3 is posted on RB: https://reviews.apache.org/r/7303/
Added retry in case of ServerNotRunningException
For the bulk assignment handling of RegionAlreadyInTransitionException, I filed
HBASE-6896. I can take care of it later on.
One question is that, in case of ServerNotRunningException, I adjust the retry
count till it is timed out, then try a new server.
Should we do not do that and let timeout monitor to handle it (i.e. fall back
to patch 2 instead)?
> All regionservers are marked offline even there is still one up
> ---------------------------------------------------------------
>
> Key: HBASE-6881
> URL: https://issues.apache.org/jira/browse/HBASE-6881
> Project: HBase
> Issue Type: Bug
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Attachments: trunk-6881.patch, trunk-6881_v3.patch
>
>
> {noformat}
> + RegionPlan newPlan = plan;
> + if (!regionAlreadyInTransitionException) {
> + // Force a new plan and reassign. Will return null if no servers.
> + newPlan = getRegionPlan(state, plan.getDestination(), true);
> + }
> + if (newPlan == null) {
> this.timeoutMonitor.setAllRegionServersOffline(true);
> LOG.warn("Unable to find a viable location to assign region " +
> state.getRegion().getRegionNameAsString());
> {noformat}
> Here, when newPlan is null, plan.getDestination() could be up actually.
--
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
