[
https://issues.apache.org/jira/browse/YARN-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075019#comment-17075019
]
Siddharth Ahuja commented on YARN-5277:
---------------------------------------
Hi [~brahmareddy] & [~vsowrirajan], thanks for your patience. I have just
finished writing up a patch for this improvement request.
This patch has re-formatted the exception message such that it now displays
local time values in ISO format for local resource's expected & actual times,
along with current time (in ISO format as well).
I have also written a comprehensive new JUnit test method that reproduces this
exception by updating the timestamp of the local resource on the filesystem to
yesterday's date just after the FSDownload object has been created but before
the download has started.
The new error message looks something like below:
{code}
java.io.IOException: Resource <resource> change on src filesystem - expected:
"2020-04-04T14:23:00.000+1100", was: "2020-04-03T14:23:00.000+1100", current
time: "2020-04-04T14:23:00.832+1100"
{code}
I'll let you (and others) to review the changes once the build passes.
> 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
> Attachments: YARN-5277.001.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
