[
https://issues.apache.org/jira/browse/HBASE-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281142#comment-16281142
]
Zach York commented on HBASE-19435:
-----------------------------------
[~tedyu] I have thought more about your infinite loop case and it doesn't seem
realistic.
In order for it to be an infinite loop, the refreshFileConnection() would have
to succeed (no IOException from re-opening the file), but then immediately get
closed before this loop completes again. This would have to happen infinitely
and I don't see any reason why that would happen.
However, if you still think this is a serious concern, I'll implement it.
> 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,
> HBASE-19435.master.002.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)
