[
https://issues.apache.org/jira/browse/HBASE-15098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096149#comment-15096149
]
Lars George commented on HBASE-15098:
-------------------------------------
Weird thing is, this was meant to be in there? See
https://github.com/apache/hbase/commit/fd37ccb63c545850c08c132b2f6470354a6629f9#diff-910fe86f307ab33e4e946c666e739972R557
Apparently https://issues.apache.org/jira/browse/HBASE-14367 removed the switch
in favor of the task always running, but then be able to enable it per table
using the shell?
Does this mean we just have to remove the configuration property from
{{hbase-default.xml}}?
> Normalizer switch in configuration is not used
> ----------------------------------------------
>
> Key: HBASE-15098
> URL: https://issues.apache.org/jira/browse/HBASE-15098
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 1.2.0
> Reporter: Lars George
> Fix For: 2.0.0, 1.2.0, 1.3.0, 1.2.1
>
>
> The newly added global switch to enable the new normalizer functionality is
> never used apparently, meaning it is always on. The {{hbase-default.xml}} has
> this:
> {noformat}
> <property>
> <name>hbase.normalizer.enabled</name>
> <value>false</value>
> <description>If set to true, Master will try to keep region size
> within each table approximately the same.</description>
> </property>
> {noformat}
> But only a test class uses it to set the switch to "true". We should
> implement a proper {{if}} statement that checks this value and properly
> disables the feature cluster wide if not wanted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
