-
Notifications
You must be signed in to change notification settings - Fork 590
HDDS-8961. [Snapshot] Added check to allow only Ozone admin user to call print compaction dag #5087
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
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.
Why the switch? Or should we just print both?
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.
It was my miss in previous PR. backwardCompactionDAG will give the same result as in https://user-images.githubusercontent.com/6820020/211372896-c4f6eada-3fb0-4838-bcc6-08c47606a43f.png
Attaching the images to differentiate.
hadoop-ozone/tools/src/main/java/org/apache/hadoop/ozone/debug/CompactionLogDagPrinter.java
Outdated
Show resolved
Hide resolved
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java
Outdated
Show resolved
Hide resolved
smengcl
left a comment
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.
Thanks @hemantk-12 for the follow-up patch. I have a few comments inline.
prashantpogde
left a comment
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.
LGTM
…in user to call print compaction dag (apache#5087) (cherry picked from commit 607b67e) Change-Id: I81515543062fb129867bba659b430db6321bf301
What changes were proposed in this pull request?
This change addresses few of the concerns raised in PR #5061.
Note: This PR doesn't addressed
Having a network call that generates a file on the server is strange.because of following reason.As we talked in here, it is better to be have it as a OM request to get the in-memory picture of the DAG. It can be solved in following two ways.
Both the solution will require more time and investigation. So for the interest of time, just addressed the security and debug message for now and create a jira: HDDS-9040 for further enhancement.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8961
How was this patch tested?
Existed unit tests.