[
https://issues.apache.org/jira/browse/HBASE-15128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168101#comment-15168101
]
Enis Soztutar commented on HBASE-15128:
---------------------------------------
Oh, sorry I thought my +1 above still stands. Usually after a +1, if the patch
author is a committer, I rely on them to fix the hadoopqa issues and do rebase
or other mechanical changes and do the commit without a further need to review.
Is javadoc warnings still applicable? Need to address those as well. You can do
it at commit time (no need for another hadoopqa run if you think that the issue
is solved).
> Disable region splits and merges switch in master
> -------------------------------------------------
>
> Key: HBASE-15128
> URL: https://issues.apache.org/jira/browse/HBASE-15128
> Project: HBase
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: Heng Chen
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-15128.patch, HBASE-15128_v1.patch,
> HBASE-15128_v3.patch, HBASE-15128_v5.patch, HBASE-15128_v6.patch,
> HBASE-15128_v7.patch
>
>
> In large clusters where region splits are frequent, and HBCK runs take
> longer, the concurrent splits cause further problems in HBCK since HBCK
> assumes a static state for the region partition map. We have just seen a case
> where HBCK undo's a concurrently splitting region causing number of
> inconsistencies to go up.
> We can have a mode in master where splits and merges are disabled like the
> balancer and catalog janitor switches. Master will reject the split requests
> if regionservers decide to split. This switch can be turned on / off by the
> admins and also automatically by HBCK while it is running (similar to
> balancer switch being disabled by HBCK).
> HBCK should also disable the Catalog Janitor just in case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
