ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19037) Clean up logs for the usage of taskId for easy lookup of command progress and status
Date Wed, 30 Nov 2016 22:47:58 GMT

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

Sumit Mohanty updated AMBARI-19037:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

committed to trunk and branch-2.5

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

Mime
View raw message