You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Li Lu (JIRA)" <ji...@apache.org> on 2014/08/01 22:53:39 UTC

[jira] [Updated] (YARN-2343) Improve error message on token expire exception

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

Li Lu updated YARN-2343:
------------------------

    Attachment: YARN-2343-080114.patch

New patch, clarified exception handling message on system time. 

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