[HDFS-17395] [FGL] Use FSLock to protect ErasureCodingPolicy related operations

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: pull-request-available
• Hadoop Flags: Reviewed
• Assignee: ZanderXu
• Reporter: ZanderXu
• Created: 22/Feb/24 07:50
• Updated: 07/Mar/24 06:12
• Resolved: 07/Mar/24 06:12

Description

NameNode supports dynamically change ErasureCodingPolicy, so these ErasureCodingPolicies should be protected by one lock, the current implementation uses the global lock.

 

ErasureCodingPolicy mainly involves directory tree and edits logs, such as:

• getErasureCodingPolicy(String src)
• setErasureCodingPolicy(String src, String ecPolicyName)
• addErasureCodingPolicies(ErasureCodingPolicy[] policies)
• disableErasureCodingPolicy(String ecPolicyName)
• enableErasureCodingPolicy(String ecPolicyName)

So we can use the FSLock to make these operations thread safe.

Another reason why we use the FSLock to protect ErasureCodingPolicy related operations is that we use FSLock to make edit write operations thread safe. 

Issue Links

• links to: GitHub Pull Request #6579