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

Hudson commented on YARN-2343:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #6000 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/6000/])
YARN-2343. Improve NMToken expire exception message. Contributed by Li Lu 
(jianhe: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1615270)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/ContainerManagerImpl.java


> Improve error message on token expire exception
> -----------------------------------------------
>
>                 Key: YARN-2343
>                 URL: https://issues.apache.org/jira/browse/YARN-2343
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Li Lu
>            Assignee: Li Lu
>            Priority: Trivial
>              Labels: usability
>             Fix For: 2.6.0
>
>         Attachments: YARN-2343-072314.patch, YARN-2343-080114.patch
>
>
> Some of token expire exception is triggered by wrong time settings on cluster 
> nodes, but the current exception message does not explicitly address that. It 
> would be helpful to add some message explicitly pointing out that this 
> exception could be caused by machines out of sync in time, or even wrong time 
> zone settings. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to