You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2021/06/10 19:57:00 UTC

[jira] [Commented] (HBASE-25651) NORMALIZER_TARGET_REGION_SIZE needs a unit in its name

    [ https://issues.apache.org/jira/browse/HBASE-25651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361199#comment-17361199 ] 

Nick Dimiduk commented on HBASE-25651:
--------------------------------------

I started the backport to branch-2, but I haven't gotten around to investigating the test failures. [~rkrahul324], do you mind picking up the pack port effort? We just need a PR against branch-2. Thanks.

> NORMALIZER_TARGET_REGION_SIZE needs a unit in its name
> ------------------------------------------------------
>
>                 Key: HBASE-25651
>                 URL: https://issues.apache.org/jira/browse/HBASE-25651
>             Project: HBase
>          Issue Type: Bug
>          Components: Normalizer
>    Affects Versions: 2.3.0
>            Reporter: Nick Dimiduk
>            Assignee: Rahul Kumar
>            Priority: Major
>             Fix For: 3.0.0-alpha-1
>
>
> On a per-table basis, the normalizer can be configured with a specific region size target via {{NORMALIZER_TARGET_REGION_SIZE}}. This value is used in a context where size values are in the megabyte scale. However, this configuration name does not mention "megabyte" or "mb" anywhere, so it's very easy for an operator to get the configured value wrong by many orders of magnitude.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)