[
https://issues.apache.org/jira/browse/HBASE-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282473#comment-16282473
]
stack commented on HBASE-19435:
-------------------------------
[~zyork] You see instances of this in prod sir? Have you tried the patch?
nit: if we fail the close here:
LOG.warn("Failed to close FileChannel", e);
... will we be able to open the file subsequently (at least there'll be a
hanging fd).
Otherwise, +1 on trying 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
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19435.branch-1.001.patch,
> HBASE-19435.master.001.patch, HBASE-19435.master.002.patch,
> HBASE-19435.master.003.patch, HBASE-19435.master.004.patch,
> HBASE-19435.master.005.patch, HBASE-19435.master.006.patch,
> HBASE-19435.master.007.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)
