You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2014/07/28 19:58:40 UTC
[jira] [Updated] (HBASE-11360) SnapshotFileCache causes too many
cache refreshes
[ https://issues.apache.org/jira/browse/HBASE-11360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-11360:
----------------------------------
Summary: SnapshotFileCache causes too many cache refreshes (was: SnapshotFileCache refresh logic based on modified directory time might be insufficient)
> SnapshotFileCache causes too many cache refreshes
> -------------------------------------------------
>
> Key: HBASE-11360
> URL: https://issues.apache.org/jira/browse/HBASE-11360
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.19
> Reporter: churro morales
> Fix For: 0.99.0, 0.98.5, 0.94.22
>
> Attachments: 11360-0.98.txt, HBASE-11360-0.94.patch, HBASE-11360-0.96.patch
>
>
> Right now we decide whether to refresh the cache based on the lastModified timestamp of all the snapshots and those "running" snapshots which is located in the /hbase/.hbase-snapshot/.tmp/<snapshot> directory
> We ran a ExportSnapshot job which takes around 7 minutes between creating the directory and copying all the files.
> Thus the modified time for the
> /hbase/.hbase-snapshot/.tmp directory was 7 minutes earlier than the modified time of the
> /hbase/.hbase-snapshot/.tmp/<snapshot> directory
> Thus the cache refresh happens and doesn't pick up all the files but thinks its up to date as the modified time of the .tmp directory never changes.
> This is a bug as when the export job starts the cache never contains the files for the "running" snapshot and will fail.
--
This message was sent by Atlassian JIRA
(v6.2#6252)