Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 11 Apr 2016 12:09:25 +0000 (UTC)
From: "Sebastian Toader (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12957400.1460165640000.191838.1460376565512@Atlassian.JIRA>
In-Reply-To: <JIRA.12957400.1460165640000@Atlassian.JIRA>
References: <JIRA.12957400.1460165640000@Atlassian.JIRA>
 <JIRA.12957400.1460165640993@arcas>
Subject: [jira] [Commented] (AMBARI-15786) Add some logs to help co-related
 task ids from server and agent
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMBARI-15786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234953#comment-15234953 ] 

Sebastian Toader commented on AMBARI-15786:
-------------------------------------------

+1

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