[
https://issues.apache.org/jira/browse/HBASE-26190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399500#comment-17399500
]
Anoop Sam John commented on HBASE-26190:
----------------------------------------
+1. We already have stats collection at BC and print that stat in every 5 mins
(by default). We can collect this stat also. Also would have been good to see
at least some log lines of this sort which says its for which file full path.
So we can know its from which table:cf.
> High rate logging of BucketAllocatorException: Allocation too big
> ------------------------------------------------------------------
>
> Key: HBASE-26190
> URL: https://issues.apache.org/jira/browse/HBASE-26190
> Project: HBase
> Issue Type: Bug
> Components: BucketCache, Operability
> Affects Versions: 2.4.5
> Reporter: Andrew Kyle Purtell
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.6
>
>
> These log lines may be printed at high frequency when using a schema that
> creates large blocks and the bucket cache is enabled. It makes sense to warn
> about this initially, but the very high rate of warnings when the use case is
> legit and this is expected does not. Print this once, then not again; or,
> rate-limit this message to be printed at a more reasonable rate, like once
> per minute.
> {noformat}
> 2021-08-11 23:42:10,902 WARN [main-BucketCacheWriter-0]
> bucket.BucketCache: Failed allocation for
> 4842189251414b8a9212f6831462e415_218610843;
> org.apache.hadoop.hbase.io.hfile.bucket.BucketAllocatorException:
> Allocation too big size=1049337;
> adjust BucketCache sizes hbase.bucketcache.bucket.sizes to accomodate
> if size seems reasonable and you want it cached.
> {noformat}
> Also, it might be better to log this at INFO given the caveat "if size seems
> reasonable and you want it cached". Reads like an informational message.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
