[
https://issues.apache.org/jira/browse/HBASE-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230899#comment-13230899
]
chunhui shen commented on HBASE-5571:
-------------------------------------
If AssignmentManager#unassign() catchs RemoteException rather than
NotServingRegionException, could we remove catching NotServingRegionException?
I'm not sure when catches RemoteException and when catches
NotServingRegionException directly, from our logs I see it catches
NotServingRegionException directly. Anyway, for this issue, we could treat
samely for the two exceptions.
> Table will be disabling forever
> -------------------------------
>
> Key: HBASE-5571
> URL: https://issues.apache.org/jira/browse/HBASE-5571
> Project: HBase
> Issue Type: Bug
> Components: master, regionserver
> Reporter: chunhui shen
> Assignee: chunhui shen
> Attachments: BASE-5571v2.patch, HBASE-5571.patch, HBASE-5571v3.patch
>
>
> If we restart master when it is disabling one table, the table will be
> disabling forever.
> In current logic, Region CLOSE RPC will always returned
> NotServingRegionException because RS has already closed the region before we
> restart master. So table will be disabling forever because the region will in
> RIT all along.
> In another case, when AssignmentManager#rebuildUserRegions(), it will put
> parent regions to AssignmentManager.regions, so we can't close these parent
> regions until it is purged by CatalogJanitor if we execute disabling the
> table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
