[
https://issues.apache.org/jira/browse/HBASE-13170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384155#comment-14384155
]
Nick Dimiduk commented on HBASE-13170:
--------------------------------------
{quote}
bq. Can we move these stack traces to debug while keeping the general error and
message at warn?
I'd rather not. for people that don't pipe all levels to one file (or use
something or than the default file loggers on log4j) it's nice to have cause
and effect in one log message.
{quote}
Cached keys expire, so it's a leak but not a WARN severity. Can they be demoted
to DEBUG at least so folk's logs aren't bloated with scary exceptions?
+1
> Allow block cache to be external
> --------------------------------
>
> Key: HBASE-13170
> URL: https://issues.apache.org/jira/browse/HBASE-13170
> Project: HBase
> Issue Type: New Feature
> Components: io
> Affects Versions: 2.0.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Fix For: 1.1.0
>
> Attachments: HBASE-13170-v1.patch, HBASE-13170-v2.patch,
> HBASE-13170-v3.patch, HBASE-13170-v4.patch, HBASE-13170.patch
>
>
> Allow an external service to provide the block cache. This has the nice
> property of allowing failover/upgrades to happen without causing a fully cold
> cache.
> Additionally this allows read replicas to share some of the same memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
