[
https://issues.apache.org/jira/browse/HBASE-9514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768579#comment-13768579
]
Enis Soztutar commented on HBASE-9514:
--------------------------------------
Raising this as a blocker is justified I believe. Note that both the balancer,
and merge's are also forcing region assignment, not just user submitted region
assignments.
bq. So I was thinking to control it from the root, AM#assign() method, the
final place an openRegion request is sent out to another RS.
Sounds good. I was thinking adding a boolean, isAssignable, to the master's in
memory state. SSH will first mark the regions as unAssignable, and log
splitting termination will reset the bit. AM#assign() will ignore regions who
are not assignable.
> Prevent region from assigning before log splitting is done
> ----------------------------------------------------------
>
> Key: HBASE-9514
> URL: https://issues.apache.org/jira/browse/HBASE-9514
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Blocker
>
> If a region is assigned before log splitting is done by the server shutdown
> handler, the edits belonging to this region in the hlogs of the dead server
> will be lost.
> Generally this is not an issue if users don't assign/unassign a region from
> hbase shell or via hbase admin. These commands are marked for experts only in
> the hbase shell help too. However, chaos monkey doesn't care.
> If we can prevent from assigning such regions in a bad time, it would make
> things a little safer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
