[
https://issues.apache.org/jira/browse/AMBARI-15786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235864#comment-15235864
]
Hudson commented on AMBARI-15786:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4633 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4633/])
AMBARI-15786. Add some logs to help co-related task ids from server and
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dcca89db5ef39b514c1d7b92cc585f46b55ef908])
* ambari-agent/src/main/python/ambari_agent/ActionQueue.py
*
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java
*
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
> Add some logs to help co-related task ids from server and agent
> ---------------------------------------------------------------
>
> Key: AMBARI-15786
> URL: https://issues.apache.org/jira/browse/AMBARI-15786
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
> Affects Versions: 2.2.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 2.2.2
>
> Attachments: AMBARI-15786.patch
>
>
> Recently, I was debugging some cluster and it was very difficult to co-relate
> commands that failed with the scheduling of commands from the server. There
> are several key log statements that are missing task IDs that can be used to
> co-relate the logs.
> The changes are modifying only the logs and I have tested that the logs are
> being emitted properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
