Liu Shaohui created HBASE-14237:
-----------------------------------
Summary: Meta region may be onlined on multi regonservers for bugs
of assigning meta
Key: HBASE-14237
URL: https://issues.apache.org/jira/browse/HBASE-14237
Project: HBase
Issue Type: Bug
Affects Versions: 0.94.11
Reporter: Liu Shaohui
Assignee: Liu Shaohui
Priority: Critical
When a regionserver failed to open the meta region and crash after setting the
RS_ZK_REGION_FAILED_OPEN state of meta region in zookeeper, the master will
handle the event of RS_ZK_REGION_FAILED_OPEN and try to assign the meta region
again in AssignmentManager#handleRegion. But at the same time, the master will
handle the regionserver expired event and start a MetaServerShutdownHandler for
the regionserver, because the servername of regionserver is same as the
servername of the unassigned node of meta region. In the
MetaServerShutdownHandler, the meta region may be assigned for second time.
[~heliangliang]
We have encountered this problem in our production cluster which resulted in
inconsistency of region location in meta table. You can see the log from the
attachment.
The code of AssignmentManager is so complex and I have not get a solution to
fix this problem. Could someone kindly help to give some suggestions? Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
