[
https://issues.apache.org/jira/browse/HBASE-27225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571584#comment-17571584
]
Hudson commented on HBASE-27225:
--------------------------------
Results for branch master
[build #642 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/642/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/642/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/642/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/642/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}
> Add BucketAllocator bucket size statistic logging
> -------------------------------------------------
>
> Key: HBASE-27225
> URL: https://issues.apache.org/jira/browse/HBASE-27225
> Project: HBase
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Assignee: Bryan Beaudreault
> Priority: Major
> Labels: patch-available
> Fix For: 2.5.1, 3.0.0-alpha-4, 2.4.14
>
>
> BucketCache places blocks into configurably sized buckets based on the block
> size. The default sizes aim to provide broad coverage for common block sizes,
> but should probably be tuned for certain use-cases. However, we provide no
> way for operators to gain insight into the distribution of buckets.
> There already exists a BucketAllocator#logStatistics method, but it is not
> called anywhere. I suggest that we hook that up in BucketCache#logStats
> (which is called periodically by a stats thread). We can go from there.
> Looking at the IndexStatistics used in that method, it looks like a good
> start. One thing I'd like to add is a count of freeBuckets and
> completelyFreeBuckets per index. I think this will be useful for indicating
> how much more wiggle room we have for redistributing buckets among the
> various block sizes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)