[ https://issues.apache.org/jira/browse/HDDS-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947700#comment-16947700 ]
Hudson commented on HDDS-2217: ------------------------------ SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17511 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/17511/]) HDDS-2217. Remove log4j and audit configuration from the docker-config (elek: rev 1f954e679895f68d6ce9e822498daa2b142e7e46) * (edit) hadoop-ozone/dist/src/main/compose/ozone-recon/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozone-hdfs/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozoneblockade/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozones3/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozonesecure-mr/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozoneperf/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozone/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozones3-haproxy/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozonesecure/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozone-mr/common-config * (edit) hadoop-ozone/dist/src/main/compose/ozone-topology/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozonescripts/docker-config * (edit) hadoop-ozone/dist/src/main/compose/ozone-om-ha/docker-config > Remove log4j and audit configuration from the docker-config files > ----------------------------------------------------------------- > > Key: HDDS-2217 > URL: https://issues.apache.org/jira/browse/HDDS-2217 > Project: Hadoop Distributed Data Store > Issue Type: Task > Components: docker > Reporter: Marton Elek > Assignee: Chris Teoh > Priority: Major > Labels: newbie, pull-request-available > Fix For: 0.5.0 > > Time Spent: 4h > Remaining Estimate: 0h > > Log4j configuration lines are added to the docker-config under > hadoop-ozone/dist/src/main/compose/... > Mainly to make it easier to reconfigure the log level of any components. > As we already have a "ozone insight" tool which can help us to modify the log > level at runtime we don't need these lines any more. > {code:java} > LOG4J.PROPERTIES_log4j.rootLogger=INFO, stdout > LOG4J.PROPERTIES_log4j.appender.stdout=org.apache.log4j.ConsoleAppender > LOG4J.PROPERTIES_log4j.appender.stdout.layout=org.apache.log4j.PatternLayout > LOG4J.PROPERTIES_log4j.appender.stdout.layout.ConversionPattern=%d{yyyy-MM-dd > HH:mm:ss} %-5p %c{1}:%L - %m%n > LOG4J.PROPERTIES_log4j.logger.org.apache.hadoop.util.NativeCodeLoader=ERROR > LOG4J.PROPERTIES_log4j.logger.org.apache.ratis.conf.ConfUtils=WARN > LOG4J.PROPERTIES_log4j.logger.org.apache.hadoop.security.ShellBasedUnixGroupsMapping=ERROR > LOG4J.PROPERTIES_log4j.logger.org.apache.ratis.grpc.client.GrpcClientProtocolClient=WARN > LOG4J.PROPERTIES_log4j.logger.http.requests.s3gateway=INFO,s3gatewayrequestlog > LOG4J.PROPERTIES_log4j.appender.s3gatewayrequestlog=org.apache.hadoop.http.HttpRequestLogAppender > LOG4J.PROPERTIES_log4j.appender.s3gatewayrequestlog.Filename=/tmp/jetty-s3gateway-yyyy_mm_dd.log > LOG4J.PROPERTIES_log4j.appender.s3gatewayrequestlog.RetainDays=3 {code} > We can remove them together with the audit log entries as we already have a > default log4j.propertes / audit log4j2 config. > After the remove the clusters should be tested: Ozone CLI should not print > and confusing log messages (such as NativeLib is missing or anything else). > AFAIK they are already turned off in the etc/hadoop/etc log4j.properties. > > -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org