[jira] [Commented] (AMBARI-18560) Add more logging to track what condition resulted in skipping agent commands

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

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

Hadoop QA commented on AMBARI-18560:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12832456/AMBARI-18560.v1.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 ambari-server.

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

This message is automatically generated.

> Add more logging to track what condition resulted in skipping agent commands
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-18560
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18560
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Sebastian Toader
>            Assignee: Sebastian Toader
>             Fix For: 2.5.0, 2.4.2
>
>         Attachments: AMBARI-18560.v1.patch
>
>
> Component START/STOP requests received through REST calls may not generate command to be executed by the agents. Currently it's hard track from the INFO level logs if commands were not sent to agents due to legitimate conditions what was the condition that resulted in skipping the creation of commands for agents.



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