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

Andrew Kyle Purtell updated HBASE-26444:
----------------------------------------
    Component/s: logging
                 Operability

> BucketCacheWriter should log only the BucketAllocatorException message, not 
> the full stack trace
> ------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-26444
>                 URL: https://issues.apache.org/jira/browse/HBASE-26444
>             Project: HBase
>          Issue Type: Task
>          Components: logging, Operability
>    Affects Versions: 2.4.8
>            Reporter: Andrew Kyle Purtell
>            Assignee: Andrew Kyle Purtell
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.9
>
>
> We have recently improved the logging of BucketAllocatorException to not 
> overwhelm the log if there are a lot of blocks that are too large, but when 
> we do log it, we still log the full stack trace. That is wasteful. The 
> messages always come from the same location in source code. The stack trace 
> provides no value.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to