-
Notifications
You must be signed in to change notification settings - Fork 621
HDDS-11509. logging improvements for directory deletion #7314
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
Changes from 1 commit
9b706bd
817dcd0
b87503e
7ffc865
42d65d0
94aae40
a466860
553815f
23cafa0
ce84054
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -402,6 +402,7 @@ public long optimizeDirDeletesAndSubmitRequest(long remainNum, | |||||
| int remainingBufLimit, KeyManager keyManager, | ||||||
| UUID expectedPreviousSnapshotId) { | ||||||
|
|
||||||
| long limit = remainNum; | ||||||
| // Optimization to handle delete sub-dir and keys to remove quickly | ||||||
| // This case will be useful to handle when depth of directory is high | ||||||
| int subdirDelNum = 0; | ||||||
|
|
@@ -452,9 +453,9 @@ public long optimizeDirDeletesAndSubmitRequest(long remainNum, | |||||
| LOG.info("Number of dirs deleted: {}, Number of sub-dir " + | ||||||
| "deleted: {}, Number of sub-files moved:" + | ||||||
| " {} to DeletedTable, Number of sub-dirs moved {} to " + | ||||||
| "DeletedDirectoryTable, iteration elapsed: {}ms," + | ||||||
| "DeletedDirectoryTable, current iteration limit: {}, iteration elapsed: {}ms," + | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also from the Jira description, we should add a WARN log when the service hits its limits, for example:
I think this needs to be added to all the deletion services. |
||||||
| " totalRunCount: {}", | ||||||
| dirNum, subdirDelNum, subFileNum, (subDirNum - subdirDelNum), | ||||||
| dirNum, subdirDelNum, subFileNum, (subDirNum - subdirDelNum), limit, | ||||||
| Time.monotonicNow() - startTime, getRunCount()); | ||||||
| } | ||||||
| return remainNum; | ||||||
|
|
||||||
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.
Logs for the total queued is good, but we should also have a similar log for each task per container queued here when it executes. Currently this is just this debug log.
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.
Do we simply convert the debug log you have pointed out to an info log, or do we want to add a info log in BlockDeletingService pointing out each container + number of blocks deleted for that container when it is added the the queue?