[ https://issues.apache.org/jira/browse/HDFS-13901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898540#comment-16898540 ]
He Xiaoqiao commented on HDFS-13901: ------------------------------------ Thanks [~LiJinglun] for your works. Just check the logic and it seems that root cause is get {{INode}} twice before hold {{readLock}}/{{writeLock}}, right? is it possible that get the last {{INode}} instance only one time and share in the whole method {{getBlockLocations}}? any other concerns? Thanks. > 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 > Attachments: HDFS-13901.000.patch, HDFS-13901.001.patch, > HDFS-13901.002.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 (v7.6.14#76016) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org