-
Notifications
You must be signed in to change notification settings - Fork 9k
HDFS-17705. Improve datasetlock related log output. #7268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@Hexiaoqiao @hfutatzhanghb Sir, please help review this PR when you have free time, Thanks a lot. |
faf0745
to
f307f49
Compare
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
@huangzhaobo99 Hi, sir. Could you please reopen this PR and rebase? |
@@ -647,8 +645,6 @@ public void removeVolumes( | |||
List<String> allSubDirNameForDataSetLock = datasetSubLockStrategy.getAllSubLockName(); | |||
for (String dir : allSubDirNameForDataSetLock) { | |||
lockManager.removeLock(LockLevel.DIR, bp, storageUuid, dir); | |||
LOG.info("Removed DIR lock for bpid:{}, volume storageid:{}, dir:{}", | |||
bp, storageUuid, dir); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we change it to debug level and add a info level log for volume-level lock.
Description of PR
Single volume has about 1000 dir locks. If there are 12 volume on dn, the logs will explode.