YARN-8226. Improved anti-affinity description in YARN Service doc.

Contributed by Gour Saha
This commit is contained in:
Eric Yang 2018-05-03 13:35:40 -04:00
parent 7fe3214d4b
commit 7698737207
2 changed files with 14 additions and 6 deletions

View File

@ -351,9 +351,13 @@ POST URL - http://localhost:8088/app/v1/services
##### GET Response JSON
GET URL - http://localhost:8088/app/v1/services/hello-world
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.
Note, for an anti-affinity component no more than 1 container will be allocated
in a specific node. In this example, 3 containers have been requested by
component "hello". All 3 containers were allocated because the cluster had 3 or
more NMs. If the cluster had less than 3 NMs then less than 3 containers would
be allocated. In cases when the number of allocated containers are less than the
number of requested containers, the component and the service will be in
non-STABLE state.
```json
{

View File

@ -766,9 +766,13 @@ POST URL - http://localhost:8088/app/v1/services
##### GET Response JSON
GET URL - http://localhost:8088/app/v1/services/hello-world
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.
Note, for an anti-affinity component no more than 1 container will be allocated
in a specific node. In this example, 3 containers have been requested by
component "hello". All 3 containers were allocated because the cluster had 3 or
more NMs. If the cluster had less than 3 NMs then less than 3 containers would
be allocated. In cases when the number of allocated containers are less than the
number of requested containers, the component and the service will be in
non-STABLE state.
```json
{