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 "Billie Rinaldi (JIRA)" <ji...@apache.org> on 2018/10/22 19:23:01 UTC
[jira] [Commented] (YARN-6167) RM option to delegate NM loss
container action to AM
[ https://issues.apache.org/jira/browse/YARN-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659496#comment-16659496 ]
Billie Rinaldi commented on YARN-6167:
--------------------------------------
Attached a first draft of this patch. I'd like to get feedback on this approach. This would require a follow-on ticket for the service AM to handle NM loss. cc [~leftnoteasy][~suma.shivaprasad]
> RM option to delegate NM loss container action to AM
> ----------------------------------------------------
>
> Key: YARN-6167
> URL: https://issues.apache.org/jira/browse/YARN-6167
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: scheduler
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Priority: Major
> Fix For: yarn-native-services
>
> Attachments: YARN-6167.01.patch
>
>
> Currently, if the RM times out an NM, the scheduler will kill all containers that were running on the NM. For some applications, in the event of a temporary NM outage, it might be better to delegate to the AM the decision whether to kill the containers and request new containers from the RM.
--
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