[ 
https://issues.apache.org/jira/browse/HBASE-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284656#comment-16284656
 ] 

Anoop Sam John commented on HBASE-19435:
----------------------------------------

Zach,  See BucketCache#evictBlocksByHfileName.. This is called after compaction 
for every file which is just compacted away.
But as Ram also said, it just removes the blocks from the 'backingMap' which is 
an on heap data structure which is having info like this block is stored in 
which bucket slot.  So it is not affecting in any way, the cached files..  But 
the more open files can be an issue? Not sure.. Because I believe in ur case 
the actual HFiles are in S3 and the BC is in local FS.

> 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: 1.4.0, 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, 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)

Reply via email to