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

2021-08-04 Thread Nick Dimiduk (Jira) 


 [ 
https://issues.apache.org/jira/browse/HBASE-25651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Dimiduk resolved HBASE-25651.
--
Resolution: Fixed

Thank you [~rkrahul324] !

> 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: 2.5.0, 3.0.0-alpha-2
>
>
> 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)

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

2021-05-28 Thread Xiaolin Ha (Jira) 


 [ 
https://issues.apache.org/jira/browse/HBASE-25651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaolin Ha resolved HBASE-25651.

Fix Version/s: 3.0.0-alpha-1
   Resolution: Fixed

Pushed to master.

Thanks [~rkrahul324] for contributing,

and thanks [~ndimiduk] [~DeanZ] for reviewing.

> 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)