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 "zhaodong (JIRA)" <ji...@apache.org> on 2018/12/03 02:34:00 UTC
[jira] [Commented] (YARN-9079) Speculative attempts should not run
on the same node
[ https://issues.apache.org/jira/browse/YARN-9079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706607#comment-16706607 ]
zhaodong commented on YARN-9079:
--------------------------------
yeah, This issue is very important for us.
> Speculative attempts should not run on the same node
> ----------------------------------------------------
>
> Key: YARN-9079
> URL: https://issues.apache.org/jira/browse/YARN-9079
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: api, capacity scheduler, yarn
> Affects Versions: 2.7.2
> Reporter: Lee chen
> Priority: Major
> Attachments: image-2018-12-03-09-54-07-859.png
>
>
> I found in all versions of yarn, Speculative Execution may set the speculative task to the node of original task.What i have read is only it will try to have one more task attempt. haven't seen any place mentioning not on same node.It is unreasonable.If the node have some problems lead to tasks execution will be very slow. and then placement the speculative task to same node cannot help the problematic task.
> In our cluster （version 2.7.2，2700 nodes），this phenomenon appear almost everyday.
> !image-2018-12-03-09-54-07-859.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org