[
https://issues.apache.org/jira/browse/HBASE-15128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122526#comment-15122526
]
Enis Soztutar commented on HBASE-15128:
---------------------------------------
bq. why a setSwitch() api instead of something like
updateConfigurationProperty() or something more generic?
Hmm, we actually do not have configuration options to enable / disable
balancer. They are usually always on of course. Only turned off in maintenance
mode. So they are really not configuration related.
bq. I prefer having the flag in normalizer, just because we keep down the
number of dynamic property that we have now. as soon as you add a generic
setSwitch() api that number will go up exponentially.
The new split or merge switch is not directly related to normalizer. It allows
to disable all splits or merges, rather than changing normalizer behavior to do
splits or merges.
> Disable region splits and merges in HBCK
> ----------------------------------------
>
> 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
>
>
> 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)
