[
https://issues.apache.org/jira/browse/YARN-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081037#comment-17081037
]
Siddharth Ahuja commented on YARN-5277:
---------------------------------------
Thank you very much for your review and commit [~snemeth]!
In regards to the following:
{bq}
Next steps:
Siddharth Ahuja: Could you please check how this would affect branch-3.3 and
branch-3.2 and if the same fix can be applied, provide patches targeting these
branches?
Thanks in advance.
{bq}
I have just uploaded a patch for branch-3.2. I am now checking branch-3.3. Will
update the JIRA soon.
> 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.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
