hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4357) Region in transition - in closing state
Date Fri, 09 Sep 2011 21:18:09 GMT

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

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

Here is the issue. It has nothing to do with master restart.

CloseRegionHandler.getCurrentVersion failed. Thus regionserver can't close the region properly.
One reason it can't get data from zookeeper could be that there are lots of regions in transition.


11/09/07 17:21:48 WARN handler.CloseRegionHandler: Error getting node's version in CLOSING
state, aborting close of miweng_500region,H\xB49X\x10bM\xB1,1315338786464.794a6ff17a4de0dd0a19b984ba18eea9.


Possible fixes:

1. Perhaps CloseRegionHandler.getCurrentVersion should retry on calls to ZKAssign.getVersion?
2. Timeout Monitor doesn't do anything for region that stays in CLOSING state for long. Perhaps
it can try to repair it like reissuing a closeregion request in RS?

> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message