[
https://issues.apache.org/jira/browse/HBASE-26340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461910#comment-17461910
]
Hudson commented on HBASE-26340:
--------------------------------
Results for branch branch-2.5
[build #6 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.5/6/]:
(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.5/6/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.5/6/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+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.5/6/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.5/6/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> TableSplit returns false size under 1MB
> ---------------------------------------
>
> Key: HBASE-26340
> URL: https://issues.apache.org/jira/browse/HBASE-26340
> Project: HBase
> Issue Type: Bug
> Components: mapreduce, regionserver
> Reporter: Norbert Kalmár
> Assignee: Norbert Kalmár
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-3, 2.4.10
>
>
> We calculate region size in the mapreduce package by getting the size in MB
> first and multiplying:
> https://github.com/apache/hbase/blob/39a20c528e2bf27cedf12734dbdb1b7b1e538076/hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mapreduce/RegionSizeCalculator.java#L87
> This will give a size of 0 until at least 1MB is reached. (And it will have
> an unwanted rounding affect as well).
> Spark for example can be tuned to do some performance tuning by eliminating
> the 0 sized regions. This will eliminate any small regions which are not
> actually empty. The hadoop interface states the size is returned in bytes,
> and while this is true do to the multiplication, we multiply by 0 until 1MB
> is reached. I'm not sure why we get the size in MB units and not in bytes
> straight up.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
