Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 11 Oct 2016 01:07:20 +0000 (UTC)
From: "Nahappan Somasundaram (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13008777.1475197264000.789005.1476148040865@Atlassian.JIRA>
In-Reply-To: <JIRA.13008777.1475197264000@Atlassian.JIRA>
References: <JIRA.13008777.1475197264000@Atlassian.JIRA> <JIRA.13008777.1475197264489@arcas>
Subject: [jira] [Commented] (AMBARI-18502) Logging of ambari agent
 scheduling activities in debug mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 11 Oct 2016 01:07:22 -0000


    [ https://issues.apache.org/jira/browse/AMBARI-18502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564069#comment-15564069 ] 

Nahappan Somasundaram commented on AMBARI-18502:
------------------------------------------------

[~rabaner]
Change looks good. A couple of nit-picks:

{code}
logger.debug("Scheduler submitting job %s to run",job.name)  // add a space before job.name
logger.debug('Worker thread starting job %s',args[0]) // add a space before args[0]
{code}

> Logging of ambari agent scheduling activities in debug mode
> -----------------------------------------------------------
>
>                 Key: AMBARI-18502
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18502
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: trunk
>            Reporter: Ranjan Banerjee
>            Priority: Minor
>              Labels: ambari-agent
>             Fix For: trunk
>
>         Attachments: AMBARI-18502.patch
>
>
> We find lots of stale alerts in Ambari. On digging deeper from the Ambari-agent logs it is found that there were many services that missed the triggering window, but no insight as to why it is missed. The aim of this is to add some debug logs on two steps primarily:
> 1)When the scheduler iterates through the jobstore and decides it is time to schedule the job.
> 2)The threadpool, being forked and executing the callback function


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