[
https://issues.apache.org/jira/browse/HBASE-13170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-13170:
----------------------------------
Attachment: HBASE-13170-v4.patch
bq.This looks great. Could you add a general description and configuration info
to the ref guide?
Let me file a follow on task for that. I am awful at documentation and it will
probably take several attempts for me to get that part good.
bq.Can we flag this as optional, with a comment that it's needed for the
external memcached blockcache?
Done
bq.Could we use an enum of external blockcache implementations that falls back
to using class names? That way we can avoid labeling bq.MemcachedBlockCache as
IO.Limited(CONFIG) because folks would just use a short name (e.g. "memcached").
Done.
bq.Please update the message to say e.g. that we're going to treat it as a
cache miss and continue.
Done.
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.
bq.I think these changes aren't related, could we move them to a different
ticket?
Done.
> 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)
