[
https://issues.apache.org/jira/browse/AMBARI-19037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15710225#comment-15710225
]
Hudson commented on AMBARI-19037:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6121 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6121/])
AMBARI-19037. Clean up logs for the usage of taskId for easy lookup of
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=32c9f5a83bef6bca90ebecb7721de256c19061c7])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
* (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java
* (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/services/RetryUpgradeActionService.java
> Clean up logs for the usage of taskId for easy lookup of command progress and
> status
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-19037
> URL: https://issues.apache.org/jira/browse/AMBARI-19037
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
> Affects Versions: 2.5.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 2.5.0
>
> Attachments: AMBARI-19037.patch
>
>
> Cleaned up usage of "taskid" in the log so that its easy to search for
> task/command life cycle events in the log.
> In general, recent logs have used the patter {{taskId = NUM}} to print out
> the log with the task Id. So just changed some of the relevant logs to use
> the same pattern.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
