[
https://issues.apache.org/jira/browse/YARN-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083190#comment-14083190
]
Hadoop QA commented on YARN-2343:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12659248/YARN-2343-080114.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4513//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4513//console
This message is automatically generated.
> 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
> 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)
