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
HDDS-2098 : Ozone shell command prints out ERROR when the log4j file … #1411
Conversation
/label ozone |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
I have a question |
Yes, while starting ozone from snapshot tar ball, it works perfectly. However, when Ozone is deployed through a cluster management tool like Cloudera Manager, the log4j properties may not be individually configurable. We may have to rely on a default log4.properties. In that case, printing a FileNotFoundException for ozone shell commands is something we can avoid. |
Thanks for fixing this @avijayanhwx. |
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.
+1.
It is fine to commit this, as we are using log4j.properties only when shell-log4j.properties file is available.
…is not present.
Manually tested change on cluster.