[
https://issues.apache.org/jira/browse/HBASE-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103254#comment-13103254
]
Ming Ma commented on HBASE-4357:
--------------------------------
Thanks, folks. I was looking into another issue in production based on 0.90.x.
Found a similar issue, instead it stays in PENDING_CLOSE state; for 0.90.x, the
state flow is different; zknode was created by RS, instead of master.
So the general scenario,
1. Regions can't be closed properly by RS for some reason.
2. RS is online from master point of view.
I will take a look first. We might have to patch for both trunk and 0.90.x.
> 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
