[
https://issues.apache.org/jira/browse/HBASE-11360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036577#comment-14036577
]
churro morales commented on HBASE-11360:
----------------------------------------
Or we could write a "inProgress" file at the start of the snapshot and have the
cache check for that file (instead of modified timestamp) then remove the file
when the snapshot is complete.
We would have to be really careful with cleanup in this case as if the file
doesn't get removed properly we could affect the performance of the
CleanerChore again.
> SnapshotFileCache refresh logic based on modified directory time might be
> insufficient
> --------------------------------------------------------------------------------------
>
> 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
>
> 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)
