You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Sebastian Toader (JIRA)" <ji...@apache.org> on 2016/10/10 11:07:20 UTC

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

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

Sebastian Toader updated AMBARI-18560:
--------------------------------------
    Attachment: AMBARI-18560.v1.patch

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