[jira] [Updated] (HBASE-27408) Improve BucketAllocatorException log to always include HFile name

["Bryan Beaudreault (Jira)" <ji...@apache.org>]

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

Bryan Beaudreault updated HBASE-27408:
--------------------------------------
    Assignee: Bryan Beaudreault
      Status: Patch Available  (was: Open)

> Improve BucketAllocatorException log to always include HFile name
> -----------------------------------------------------------------
>
>                 Key: HBASE-27408
>                 URL: https://issues.apache.org/jira/browse/HBASE-27408
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Bryan Beaudreault
>            Assignee: Bryan Beaudreault
>            Priority: Major
>
> In HBASE-26444 the logging around BucketAllocatorException was improved. One thing I'm noticing is that I'm often seeing logs like this:
> {quote}2022-10-03T13:13:18,284 [main-BucketCacheWriter-0] WARN org.apache.hadoop.hbase.io.hfile.bucket.BucketCache: Most recent failed allocation after 60000 ms; Message: Allocation too big size=771956; adjust BucketCache sizes hbase.bucketcache.bucket.sizes to accomodate if size seems reasonable and you want it cached.
> {quote}
> According to the logic in the code, this means the failure was for an HFileBlock but the block's getColumnFamily and/or getTableName were null. I'm not sure why that is the case, we don't have any special customizations here. But as a result we don't print any indication of the hfile name. We should add an option to fallback here on the default printing which includes the re.getKey() (HFile name) in all cases.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)