[HDFS-6294] Use INode IDs to avoid conflicts when a file open for write is renamed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.20.1
• Fix Version/s: 2.5.0
• Component/s: namenode
• Target Version/s: 2.5.0
• Assignee: Colin McCabe
• Reporter: Colin McCabe
• Created: 28/Apr/14 17:39
• Updated: 13/Oct/17 14:49
• Resolved: 09/May/14 22:55

Description

Now that we have a unique INode ID for each INode, clients with files that are open for write can use this unique ID rather than a file path when they are requesting more blocks or closing the open file. This will avoid conflicts when a file which is open for write is renamed, and another file with that name is created.

Issue Links

• is duplicated by: HDFS-4437 Clients should not retain leases on moved files
• is duplicated by: HDFS-4258 Rename of Being Written Files
• is related to: HDFS-4437 Clients should not retain leases on moved files
• is related to: HDFS-4258 Rename of Being Written Files
• relates to: HDFS-12657 Operations based on inode id must not fallback to the path
• relates to: HDFS-10869 Remove the unused method InodeId#checkId()