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

Siddharth Ahuja commented on YARN-5277:
---------------------------------------

Hi [~snemeth], patches for both the branches (3.2 & 3.3) have been built 
successfully (kindly see the results above). As such, please feel free to 
commit them in the appropriate branches. Thanks in advance for your assistance!

> 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
>             Fix For: 3.4.0
>
>         Attachments: YARN-5277-branch-3.2.003.patch, 
> YARN-5277-branch-3.3.004.patch, YARN-5277.001.patch, YARN-5277.002.patch
>
>
> 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