You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2014/03/03 16:51:21 UTC
[jira] [Resolved] (AMBARI-4917) when pushing a large config file
(like log4j), don't show all content in log
[ https://issues.apache.org/jira/browse/AMBARI-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Sen resolved AMBARI-4917.
--------------------------------
Resolution: Fixed
Committted to trunk b1ad9ea73e47167e64380fb8fdf08a3738836d3c
> when pushing a large config file (like log4j), don't show all content in log
> ----------------------------------------------------------------------------
>
> Key: AMBARI-4917
> URL: https://issues.apache.org/jira/browse/AMBARI-4917
> Project: Ambari
> Issue Type: Task
> Components: agent
> Affects Versions: 1.5.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Fix For: 1.5.0
>
>
> Update a Service config that has log4j properties (for example, Hive). On restart when the configs are pushed, all the log4j content is in the log. This is a lot to show. Long messages should be truncated
--
This message was sent by Atlassian JIRA
(v6.2#6252)