[HDFS-13901] INode access time is ignored because of race between open and rename

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.0, 2.8.6, 2.9.3, 3.1.4, 3.2.2, 2.10.1
• Assignee: Jinglun
• Reporter: Jinglun
• Created: 06/Sep/18 13:11
• Updated: 02/Jul/21 17:57
• Resolved: 23/Oct/19 01:57

Description

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. 

Issue Links

• Blocked: HDFS-9477 namenode starts failed:FSEditLogLoader: Encountered exception on operation TimesOp
• Blocked: HDFS-8269 getBlockLocations() does not resolve the .reserved path and generates incorrect edit logs when updating the atime
• relates to: HDFS-14529 SetTimes to throw FileNotFoundException if inode is not found
• relates to: HDFS-7463 Simplify FSNamesystem#getBlockLocationsUpdateTimes