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 "Prabhu Joseph (Jira)" <ji...@apache.org> on 2020/07/22 08:48:00 UTC
[jira] [Updated] (YARN-10357) Proactively relocate allocated
containers from a stopped node
[ https://issues.apache.org/jira/browse/YARN-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prabhu Joseph updated YARN-10357:
---------------------------------
Parent: YARN-5139
Issue Type: Sub-task (was: Improvement)
> Proactively relocate allocated containers from a stopped node
> -------------------------------------------------------------
>
> Key: YARN-10357
> URL: https://issues.apache.org/jira/browse/YARN-10357
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacityscheduler, multi-node-placement
> Affects Versions: 3.4.0
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Major
>
> In a cloud environment, node can be frequently commissioned, if we always wait for 10 mins timeout, it may not be good, it's better to improve the logic by preempting containers newly allocated (by not acquired) on NM which stopped heartbeating. With this, we can proactively relocate containers to different nodes before the 10 mins timeout.
> cc [~leftnoteasy]
--
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