ZanderXu opened a new pull request, #6579: URL: https://github.com/apache/hadoop/pull/6579
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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
