[HDFS-17385] [FGL] Replace the global FS write locking with directory tree-based fine-grained locking

• Type: Improvement
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Labels: FGL
• Assignee: ZanderXu
• Reporter: ZanderXu
• Created: 19/Feb/24 06:58
• Updated: 07/May/24 07:06

Description

Second, we can replace the global FS write locking with directory tree-based fine-grained locking.

This ticket doesn't remove this global FS locking, it just replaces the global FS write lock with the global FS read lock and directory tree-based fine-grained lock.

For block-related operations and DN-related operations still need the global BM lock.

 

The lock order should be:

• The global FS lock
• The global BM lock
• The directory tree-based fine-grained lock

 

This ticket should supports:

• End-user can choose lock mode
  • One global lock mode
  • Global FS lock and global BM lock mode
  • Global FS read lock, global BM lock and tree-based fine-grained lock

Issue Links

• Is contained by: HDFS-17366 NameNode Fine-Grained Locking via Namespace Tree

Sub-Tasks

• [FGL] Make INodeMap thread safe: Open
• [FGL] Implement a LockPool: In Progress
• [FGL] Make INodesInPath closeable: In Progress
• [FGL] Make getFullPathName in INode.java thread safe: In Progress
• [FGL] Abstract lock mode to cover all RPCs: Open
• [FGL] Abstract a INodeLockManager to manage acquiring and releasing locks in the directory-tree [I]: Open
• [FGL] GetFileInfo supports fine-grained locking: Open
• [FGL] Create RPC supports fine-grained Locking: Open
• [FGL] Make rollEdits thread safe: Open