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

Venkata krishnan Sowrirajan commented on YARN-5277:
---------------------------------------------------

[~sahuja] Are you still working on a fix for this issue? We are also hitting 
this issue while running Spark on Yarn. It would be great if you can post the 
patch or give more info. Thanks

> when localizers fail due to resource timestamps being out, provide more 
> diagnostics
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-5277
>                 URL: https://issues.apache.org/jira/browse/YARN-5277
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Assignee: Siddharth Ahuja
>            Priority: Major
>
> When an NM fails a resource D/L as the timestamps are wrong, there's not much 
> info, just two long values. 
> It would be good to also include the local time values, *and the current wall 
> time*. These are the things people need to know when trying to work out what 
> went wrong



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to