[ https://issues.apache.org/jira/browse/HDDS-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639872#comment-16639872 ]
Dinesh Chitlangia commented on HDDS-578: ---------------------------------------- [~elek] - Thanks for review and commit. {quote}(BTW. As I see by default we logs everything to the std output. So we don't need to add all the audit specific lines to the docker-config files as the default should be enough and usually we don't need to change it. {quote} For audit, it was done this way so that the console/logs don't get flooded with auditĀ log messagesĀ even when using via docker and checking exception of other issues might become painful. Imagine if you were to run freon :) > om-audit-log4j2.properties must be packaged in ozone-dist > ---------------------------------------------------------- > > Key: HDDS-578 > URL: https://issues.apache.org/jira/browse/HDDS-578 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Manager > Reporter: Dinesh Chitlangia > Assignee: Dinesh Chitlangia > Priority: Major > Labels: regression > Fix For: 0.3.0 > > Attachments: HDDS-578.001.patch > > > After HDDS-447, it appears the om-audit-log4j2.properties file is not > available ozone tar ball. > On decompressing the ozone tar, we must see this file in > ozone-<version>/etc/hadoop directory. > This Jira aims to fix this so that audit logging configurations are available > and logs are generated. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org