You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2014/03/20 17:56:47 UTC

[jira] [Updated] (AMBARI-5147) log4j configs to be applied after Ambari upgrade

     [ https://issues.apache.org/jira/browse/AMBARI-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahadev konar updated AMBARI-5147:
----------------------------------

    Assignee: Dmytro Sen

> log4j configs to be applied after Ambari upgrade
> ------------------------------------------------
>
>                 Key: AMBARI-5147
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5147
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.5.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 1.5.0
>
>
> As a part of ambari upgrade, customized log4j properties for HDP services must be imported into *-log4j configs(hdfs-log4j, hbase-log4j, etc.). 
> Proposals:
> 1. "ambari-server upgrade" command runs separate java software, which connects to the Ambari DB and creates required *-log4j configs. Admin should provide all log4j.properties files, for instance, copy them to predefined directory on ambari-server node.



--
This message was sent by Atlassian JIRA
(v6.2#6252)