Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 11 Feb 2016 10:49:18 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12937838.1455017035000.25039.1455187758227@Atlassian.JIRA>
In-Reply-To: <JIRA.12937838.1455017035000@Atlassian.JIRA>
References: <JIRA.12937838.1455017035000@Atlassian.JIRA>
 <JIRA.12937838.1455017035668@arcas>
Subject: [jira] [Updated] (YARN-4682) AMRM client to log when AMRM token
 updated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Steve Loughran updated YARN-4682:
---------------------------------
    Attachment: YARN-4682-002.patch

the issue is just that the lines of code above your patch had changed, so the diff wouldn't take. This is the patch with that changed; if jenkins/yetus is happy, i'll commit it

> AMRM client to log when AMRM token updated
> ------------------------------------------
>
>                 Key: YARN-4682
>                 URL: https://issues.apache.org/jira/browse/YARN-4682
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 2.7.2
>            Reporter: Steve Loughran
>         Attachments: YARN-4682-002.patch, YARN-4682.patch, YARN-4682.patch.1
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> There's no information right now as to when the AMRM token gets updated; if something has gone wrong with the update, you can't tell when it last when through.
> fix: add a log statement.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)