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

Hudson commented on HBASE-25651:
--------------------------------

Results for branch branch-2
        [build #314 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/314/]:
 (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/314/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/314/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/314/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/314/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console 
output|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/314//console].


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

Reply via email to