[ https://issues.apache.org/jira/browse/HDFS-13901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei-Chiu Chuang updated HDFS-13901: ----------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed the patch all the way from trunk to branch-2.8. Thanks [~LiJinglun]! > 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, 2.8.6, 2.9.3, 3.1.4, 3.2.2, 2.10.1 > > Attachments: HDFS-13901-branch-3.2.001.patch, 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, HDFS-13901.branch-2.001.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-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org