[
https://issues.apache.org/jira/browse/HBASE-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279709#comment-16279709
]
ramkrishna.s.vasudevan commented on HBASE-19435:
------------------------------------------------
bq.If there is an HBase thread that keeps interrupting that connection, we
should fix the error there. Currently, I believe we are seeing this in some
case where a compaction interrupts the connection, but haven't isolated the
specific process.
I think immediate refresh is fine here but on the point that you see compaction
interrupting the file connection - are you saying about the forceful eviction
of the cache blocks when a compaction happens?
For re enabling the cache I think yes that needs to be done for cases as this.
Because even if it is invalidated we need the cache back if the bucket cache's
file connection is back.
> Reopen Files for ClosedChannelException in BucketCache
> ------------------------------------------------------
>
> Key: HBASE-19435
> URL: https://issues.apache.org/jira/browse/HBASE-19435
> Project: HBase
> Issue Type: Bug
> Components: BucketCache
> Affects Versions: 2.0.0, 1.3.1
> Reporter: Zach York
> Assignee: Zach York
> Attachments: HBASE-19435.master.001.patch
>
>
> When using the FileIOEngine for BucketCache, the cache will be disabled if
> the connection is interrupted or closed. HBase will then get
> ClosedChannelExceptions trying to access the file. After 60s, the RS will
> disable the cache. This causes severe read performance degradation for
> workloads that rely on this cache. FileIOEngine never tries to reopen the
> connection. This JIRA is to reopen files when the BucketCache encounters a
> ClosedChannelException.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
