Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 19 Mar 2014 18:57:42 +0000 (UTC)
From: "Dmytro Sen (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12702457.1395255383982.105639.1395255462906@arcas>
In-Reply-To: <JIRA.12702457.1395255383982@arcas>
References: <JIRA.12702457.1395255383982@arcas>
Subject: [jira] [Created] (AMBARI-5147) log4j configs to be applied after
 Ambari upgrade
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Dmytro Sen created AMBARI-5147:
----------------------------------

             Summary: 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
            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)