[
https://issues.apache.org/jira/browse/HBASE-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-9696:
-------------------------------
Attachment: trunk-9696.patch
Attached a patch that contains the following changes:
1. introduced two new states for region to be created at merging/splitting.
don't have good names for them.
2. changed the payload of RegionTransition for merging/splitting, so that the
new region info is also passed to master when the process started. Therefore,
we can simplify the processing of these events, and make sure the new region
can't be moved after the process is done, so that they can be closed properly
when moving.
3. handled merging region at master recovery properly.
4. added test for 3.
5. some code consolidation with Split/MergeRegionHandler
> Master recovery ignores online merge znode
> ------------------------------------------
>
> Key: HBASE-9696
> URL: https://issues.apache.org/jira/browse/HBASE-9696
> Project: HBase
> Issue Type: Bug
> Components: master, Region Assignment
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Attachments: trunk-9696.patch
>
>
> The online merge znode uses the new region to be created. When master
> restarts, the new region is still unknown if the merging is not completed.
> Therefore the znode is ignored, which should not. That means the two merging
> regions could be moved around. This could cause some data loss if we are not
> luck.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
