ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13310) alerts should log into ambari-agent.log rather than to ambari-agent.out
Date Mon, 05 Oct 2015 12:07:26 GMT

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

Andrew Onischuk updated AMBARI-13310:
-------------------------------------
    Description: The problem is that ambari-agent.out is not rolled and if ambari-agent is
started for a long time, the out grows too huge. Also it's usefull to see alerts time in logs.

> alerts should log into ambari-agent.log rather than to ambari-agent.out
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-13310
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13310
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.2.0
>
>
> The problem is that ambari-agent.out is not rolled and if ambari-agent is started for
a long time, the out grows too huge. Also it's usefull to see alerts time in logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message