[jira] [Commented] (AMBARI-18502) Logging of ambari agent scheduling activities in debug mode

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-18502:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12832575/AMBARI-18502.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:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/8839//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8839//console

This message is automatically generated.

> 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)