[
https://issues.apache.org/jira/browse/HBASE-12629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234927#comment-14234927
]
Enis Soztutar commented on HBASE-12629:
---------------------------------------
It depends. I like having safe-guards in the code, even it is not documented.
At least if an issue comes up in production, and if you can identify the issue
than you can disable the feature as a stop gap without having to deploy new
code. For this particular feature, the MR job does not need the region size
calculation at all. It is just there as for some human to better monitor the
job. Thus, if it causes extra NN load or something, we can turn it off.
> Remove hbase.regionsizecalculator.enable from RegionSizeCalculator
> ------------------------------------------------------------------
>
> Key: HBASE-12629
> URL: https://issues.apache.org/jira/browse/HBASE-12629
> Project: HBase
> Issue Type: Improvement
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Fix For: 1.0.0, 2.0.0
>
> Attachments:
> 0001-HBASE-12629-Remove-hbase.regionsizecalculator.enable.patch
>
>
> The RegionSizeCalculator has a option to disable it. It is on by default and
> end-to-end use with it disabled is not tested or used anywhere except for a
> simple unit test. This removes it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
