You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2019/10/22 00:37:00 UTC
[jira] [Updated] (HDFS-13901) INode access time is ignored because
of race between open and rename
[ https://issues.apache.org/jira/browse/HDFS-13901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei-Chiu Chuang updated HDFS-13901:
-----------------------------------
Fix Version/s: 3.3.0
> INode access time is ignored because of race between open and rename
> --------------------------------------------------------------------
>
> Key: HDFS-13901
> URL: https://issues.apache.org/jira/browse/HDFS-13901
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Jinglun
> Assignee: Jinglun
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: HDFS-13901.000.patch, HDFS-13901.001.patch, HDFS-13901.002.patch, HDFS-13901.003.patch, HDFS-13901.004.patch, HDFS-13901.005.patch, HDFS-13901.006.patch, HDFS-13901.007.patch
>
>
> That's because in getBlockLocations there is a gap between readUnlock and re-fetch write lock (to update access time). If a rename operation occurs in the gap, the update of access time will be ignored. We can calculate new path from the inode and use the new path to update access time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org