You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/05/29 21:54:20 UTC
[jira] [Commented] (AMBARI-2220) Update deployed log4j conf for
Hbase deployments from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669632#comment-13669632 ]
Sumit Mohanty commented on AMBARI-2220:
---------------------------------------
LGTM, +1
> Update deployed log4j conf for Hbase deployments from Ambari
> ------------------------------------------------------------
>
> Key: AMBARI-2220
> URL: https://issues.apache.org/jira/browse/AMBARI-2220
> Project: Ambari
> Issue Type: Improvement
> Components: agent
> Affects Versions: 1.2.4
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.2.4
>
> Attachments: AMBARI-2220.patch
>
>
> HBase has updated log4.properties file to add some audit logging. It seems that we are not picking the log4j version that we deploy by default from the hbase package. We should either
> 1. Pick the log4j default config from upstream unless we are changing it
> 2. Update default log4j configs manually for every release whenever defaults in hbase changes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira