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

Ming Ma commented on HBASE-4357:
--------------------------------

How about the followings, similar to how OPENING is handled?

1. If closeRegion fails for some reason, RS will transition ZK state to a new 
state ZK_FAILED_CLOSE. AM will reissue closeRegion request to the same RS right 
away.
2. closeRegion operation could take a long time, doing flush, etc. It will do 
tickClosing so AM's timeoutMonitor won't kick in.
3. When AM's timeoutMonitor kicks in, it will try to reissue closeRegion to the 
same RS. However, if the RS stays in closing the region due to some bug, not 
sure if reissuing closeRegion will help much. Instead, could Master restarts 
the RS instead?
                
> Region in transition - in closing state
> ---------------------------------------
>
>                 Key: HBASE-4357
>                 URL: https://issues.apache.org/jira/browse/HBASE-4357
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>
> Got the following during testing, 
> 1. On a given machine, kill "RS process id". Then kill "HMaster process id".
> 2. Start RS first via "bin/hbase-daemon.sh --config ./conf start 
> regionserver.". Start HMaster via "bin/hbase-daemon.sh --config ./conf start 
> master".
> One region of a table stayed in closing state.
> According to zookeeper,
> 794a6ff17a4de0dd0a19b984ba18eea9 
> miweng_500region,H\xB49X\x10bM\xB1,1315338786464.794a6ff17a4de0dd0a19b984ba18eea9.
>  state=CLOSING, ts=Wed Sep 07 17:21:44 PDT 2011 (75701s ago), 
> server=sea-esxi-0,60000,1315428682281 
> According to .META. table, the region has been assigned to from sea-esxi-0 to 
> sea-esxi-4.
> miweng_500region,H\xB49X\x10bM\xB1,1315338786464.794a6ff17a4de0dd0a19b984ba18eea9.
>  sea-esxi-4:60030  H\xB49X\x10bM\xB1 I7K\xC6\xA7\xEF\x9D\x90 0 

--
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

        

Reply via email to