-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDDS-2217. Removed redundant LOG4J lines from docker configurations #1582
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
|
/label ozone |
|
/retest |
|
💔 -1 overall
This message was automatically generated. |
|
ci/acceptance appears to be no failing tests. |
elek
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.
Thank you very much the patch @christeoh This part looks good to me, but can you please remove the LOG4J2_.... lines as well.
Just as a background:
Audit logging uses a different logger (log4j2) than the normal logging (log4j1). But we don't use the generated log4j2 files at all (=generated based on these environment variables) as the ./bin/ozone shell script configure specific audit log files:
For example:
HDFS_OM_OPTS="${HDFS_OM_OPTS} -Dlog4j.configurationFile=${HADOOP_CONF_DIR}/om-audit-log4j2.properties"
So we can just remove them.
|
💔 -1 overall
This message was automatically generated. |
|
/retest |
|
💔 -1 overall
This message was automatically generated. |
|
Looks like there's some issues with Ratis? Is this related to the patch? |
|
If you think about the integration tests, they are independent (I am working to remove that noise). I don't know what has been happened but I think you did some merge instead of rebase. Behind this link: https://github.com/apache/hadoop/pull/1582/files I see hundred of files which are changed but ideally only docker-config files should be there. Try: (Or ping me offline if you have problems...) |
|
/retest |
|
💔 -1 overall
This message was automatically generated. |
|
It looks like the yarn resource manager was killed: rm_1 | /opt/launcher/plugins/800_launch/launch.sh: line 5: 70 Killed yarn resourcemanager |
|
/retest |
elek
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.
rm_1 | /opt/launcher/plugins/800_launch/launch.sh: line 5: 70 Killed yarn resourcemanager
Can be some environment specific issue. I run the hadoop27 m3 multiple times locally and worked well.
- 1 for the patch. Thank you very much the contribution. Will commit it to the trunk, soon.
(During the commit I also removed three additional, remaining LOG4J from ozonesecure. They can be removed and replaced with insight log level deifnition...)
|
Thanks very much for your help @elek and @anuengineer. Onward and upward. |
Removed potentially confusing LOG4J lines from docker configuration