You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/05/15 17:26:01 UTC
[jira] [Commented] (AMBARI-11167) Move alert success logs to DEBUG
level
[ https://issues.apache.org/jira/browse/AMBARI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545665#comment-14545665 ]
Hadoop QA commented on AMBARI-11167:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12733129/AMBARI-11167.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{color:red}-1 javac{color:red}. The patch appears to cause the build to fail.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2740//console
This message is automatically generated.
> Move alert success logs to DEBUG level
> --------------------------------------
>
> Key: AMBARI-11167
> URL: https://issues.apache.org/jira/browse/AMBARI-11167
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.1.0
>
> Attachments: AMBARI-11167.patch
>
>
> agent log has a lot of success logs for alerts. They should be moved to DEBUG level. For example:
> {noformat}
> INFO 2015-04-28 05:48:59,243 scheduler.py:527 - Job "14094bc0-211f-41c3-ae15-cc3c63a9de65 (trigger: interval[0:01:00], next run at: 2015-04-28 05:49:58.815287)" executed successfully
> INFO 2015-04-28 05:48:59,244 scheduler.py:509 - Running job "4594451f-266c-4cf6-855d-34f746e5cdef (trigger: interval[0:01:00], next run at: 2015-04-28 05:48:58.815473)" (scheduled at 2015-04-28 05:48:58.815473)
> INFO 2015-04-28 05:48:59,249 scheduler.py:509 - Running job "4acc8bc2-4c2f-4da3-a498-91fd420aad6a (trigger: interval[0:01:00], next run at: 2015-04-28 05:48:58.815646)" (scheduled at 2015-04-28 05:48:58.815646)
> INFO 2015-04-28 05:48:59,250 scheduler.py:527 - Job "4acc8bc2-4c2f-4da3-a498-91fd420aad6a (trigger: interval[0:01:00], next run at: 2015-04-28 05:48:58.815646)" executed successfully
> INFO 2015-04-28 05:48:59,258 scheduler.py:509 - Running job "a0ac486b-a1c1-4477-b069-be2697f4c8e6 (trigger: interval[0:02:00], next run at: 2015-04-28 05:48:58.815818)" (scheduled at 2015-04-28 05:48:58.815818)
> INFO 2015-04-28 05:48:59,266 scheduler.py:509 - Running job "46a8e05d-ec9a-4545-a465-e72edf227176 (trigger: interval[0:02:00], next run at: 2015-04-28 05:48:58.815991)" (scheduled at 2015-04-28 05:48:58.815991)
> INFO 2015-04-28 05:48:59,268 scheduler.py:527 - Job "4594451f-266c-4cf6-855d-34f746e5cdef (trigger: interval[0:01:00], next run at: 2015-04-28 05:49:58.815473)" executed successfully
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)