[
https://issues.apache.org/jira/browse/HBASE-21070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595745#comment-16595745
]
Zach York commented on HBASE-21070:
-----------------------------------
Good catch on readLock, missed removing that.
The volatile keyword is still needed because even if these methods are
synchronized, a different thread might have an old reference (which I believe
is what happened in my testing).
Let me think again on a UT... I couldn't find a good way to test this
functionality, but maybe I can extend FileSystem to make a mock filesystem that
can behave how I want it.
Thanks for the review [~liuml07]!
> SnapshotFileCache won't update for snapshots stored in S3
> ---------------------------------------------------------
>
> Key: HBASE-21070
> URL: https://issues.apache.org/jira/browse/HBASE-21070
> Project: HBase
> Issue Type: Bug
> Components: snapshots
> Affects Versions: 3.0.0, 2.1.1, 1.4.7
> Reporter: Zach York
> Assignee: Zach York
> Priority: Critical
> Labels: FSRedo
> Attachments: HBASE-21070.master.001.patch,
> HBASE-21070.master.002.patch
>
>
> The SnapshotFileCache depends on last modified time to determine whether to
> update the Snapshot HFile cache. However, in S3, real 'folders' don't exist.
> S3 filesystems create a dummy file in place of a folder, but the dummy file
> last modified time is not updated when files are changed 'under' it. This
> means that the SnapshotFileCache doesn't pick up new snapshot HFiles and
> these files aren't removed from the HFileCleaner and can be eligible for
> deletion.
>
> My patch removes the lastmodified assumption.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
