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 "Adam Antal (Jira)" <ji...@apache.org> on 2019/09/27 07:40:00 UTC
[jira] [Comment Edited] (YARN-5277) when localizers fail due to
resource timestamps being out, provide more diagnostics
[ https://issues.apache.org/jira/browse/YARN-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939189#comment-16939189 ]
Adam Antal edited comment on YARN-5277 at 9/27/19 7:39 AM:
-----------------------------------------------------------
Customer of ours is hitting this. If [~stevel@apache.org] is not working on this/does not have a patch, someone else could grab this.
was (Author: adam.antal):
Customer of ours is hitting this. If [~stevel@apache.org] is not working on this/does not have a patch, someone could grab this.
> 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
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org