[
https://issues.apache.org/jira/browse/AMBARI-18560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562660#comment-15562660
]
Hudson commented on AMBARI-18560:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5779 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5779/])
AMBARI-18560. Add more logging to track what condition resulted in (stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2d1d5f9b00e39a137c5aea8341436f408975cf82])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ServiceComponentHostRequest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostComponentResourceProvider.java
> 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)
