[
https://issues.apache.org/jira/browse/HDDS-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612255#comment-16612255
]
Elek, Marton commented on HDDS-423:
-----------------------------------
[~xyao] This is a deployment time workaround. I just overwrite the existing
log4j.properties in etc/hadoop/log4j.properties with an ozone specific one. We
have only one log4j.properties on the classpath.
[~anu] Good question. I don't know. As Ozone could be started as a hdfs
datanode plugin, it could be useful. But maybe it's more clean to remove all
the ozone specific lines from the hadoop log4j and put back only if it's
required. The ozone specific log4j properties also could be simplified, the
hdfs only features could be removed. As of now I was lazy I just copied the
existing one to make it possible to solve the logger problem, but we can also
consolidate all the log4j settings of the ozone (but it could be for 0.3.0)
> Introduce an ozone specific log4j.properties
> --------------------------------------------
>
> Key: HDDS-423
> URL: https://issues.apache.org/jira/browse/HDDS-423
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Minor
> Fix For: 0.2.1
>
> Attachments: HDDS-423-ozone-0.2.1.001.patch
>
>
> Currently the ozone distribution uses the common log4j.properties from the
> hadoop-common project.
>
> For this reason it's very hard to define default settings just for the ozone.
> For example for ozone we can turn off the warning of the NativeCodeLoader
>
> I propose to maintain an ozone specific version of the log4j.properties and
> adjust the log level of the NativeCodeLoader and ratis ConfUtils there
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
