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 "Sunil Govindan (JIRA)" <ji...@apache.org> on 2018/11/06 13:16:01 UTC
[jira] [Updated] (YARN-8226) Improve anti-affinity section
description in YARN Service API doc
[ https://issues.apache.org/jira/browse/YARN-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunil Govindan updated YARN-8226:
---------------------------------
Fix Version/s: 3.3.0
3.1.2
3.2.0
> Improve anti-affinity section description in YARN Service API doc
> -----------------------------------------------------------------
>
> Key: YARN-8226
> URL: https://issues.apache.org/jira/browse/YARN-8226
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: docs, documentation
> Reporter: Charan Hebri
> Assignee: Gour Saha
> Priority: Major
> Fix For: 3.2.0, 3.1.2, 3.3.0
>
> Attachments: YARN-8226.01.patch
>
>
> The anti-affinity section in the YARN services doc says,
> {noformat}
> Note, that the 3 containers will come up on 3 different nodes. If there are less than 3 NMs running in the cluster, then all 3 container requests will not be fulfilled and the service will be in non-STABLE state.{noformat}
> Based on the description the expected behavior for the case of number of NMs less than the number of containers requested isn't very obvious. Opening issue to improve the comment.
--
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