[
https://issues.apache.org/jira/browse/YARN-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462884#comment-16462884
]
Hudson commented on YARN-8226:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14120 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14120/])
YARN-8226. Improved anti-affinity description in YARN Service doc.
(eyang: rev 7698737207b01e80b1be2b4df60363f952a1c2b4)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/YarnServiceAPI.md
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services-api/src/main/resources/definition/YARN-Services-Examples.md
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
