You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Zhihong Yu (Commented) (JIRA)" <ji...@apache.org> on 2012/01/07 00:00:40 UTC

[jira] [Commented] (HBASE-4357) Region stayed in transition - in closing state

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

Zhihong Yu commented on HBASE-4357:
-----------------------------------

Integrated to 0.92 and TRUNK.

Thanks for the patch, Ming. You correctly generated patch for 0.92 but Hadoop QA runs test suite in TRUNK.

Thanks for the review Ram.
                
> Region stayed in transition - in closing state
> ----------------------------------------------
>
>                 Key: HBASE-4357
>                 URL: https://issues.apache.org/jira/browse/HBASE-4357
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.0
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>             Fix For: 0.92.0, 0.94.0
>
>         Attachments: 4357.txt, HBASE-4357-0.92.patch
>
>
> 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