[
https://issues.apache.org/jira/browse/HBASE-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182114#comment-13182114
]
stack commented on HBASE-4357:
------------------------------
+1 Nice patch Ming.
Regards conversation above on what if HRS can't close a region, I'd say lets go
basic for now and crash out the HRS and let ServerShutdownHandler make sense of
it all. Not the TimeoutMonitor IMO. TM at the moment is way too heavy-handed.
Needs to be made more of a butterfly than bulldozer before we let it do
closing fixups.
Good stuff.
> 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
