You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2021/10/21 01:52:00 UTC

[jira] [Reopened] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

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

Andrew Kyle Purtell reopened HBASE-26190:
-----------------------------------------

Is it just me or is this not terribly useful? 

{noformat}
2021-10-21 01:48:42,860 WARN  [main-BucketCacheWriter-0] bucket.BucketCache: Most recent failed allocation in 60000 milliseconds; Table
Name = null, Column Family = null, HFile Name : 1919692f80b841b7a3d4453ec01186f1
org.apache.hadoop.hbase.io.hfile.bucket.BucketAllocatorException: Allocation too big size=1050637; adjust BucketCache sizes hbase.bucket
cache.bucket.sizes to accomodate if size seems reasonable and you want it cached.
{noformat}

Table is always null and column family is always null in these messages. This is with latest branch-2.4. I think this should be corrected now with an addendum or this should be reverted and improved later. [~anoop.hbase]

> 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
>            Assignee: Kulwant Singh
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.8
>
>
> 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)