[
https://issues.apache.org/jira/browse/YARN-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi updated YARN-6405:
---------------------------------
Attachment: unique-names-test.patch
[~jianhe], there is a problem with unique names with this patch. I tried fixing
the unique names unit test to verify the role instances are named properly and
that's how I noticed the problem. I attached the diff I was using
(unique-names-test.patch). Instead of having a fixed set of names 1 to N, when
a container goes down and comes back up it will have name N+1, and there will
be no container with the original name. The second container to go down will
come back with name N+2, etc.
I haven't looked at the rest of the patch yet, but I will do so tomorrow.
> Improve configuring services through REST API
> ---------------------------------------------
>
> Key: YARN-6405
> URL: https://issues.apache.org/jira/browse/YARN-6405
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Jian He
> Assignee: Jian He
> Attachments: unique-names-test.patch,
> YARN-6405.yarn-native-services.01.patch,
> YARN-6405.yarn-native-services.02.patch,
> YARN-6405.yarn-native-services.03.patch,
> YARN-6405.yarn-native-services.04.patch,
> YARN-6405.yarn-native-services.05.patch,
> YARN-6405.yarn-native-services.06.patch
>
>
> YARN-4793 defined various ways that user can config services through the
> configuration section of the REST API. But, some semantics are not yet
> supported in the back-end server (AM). YARN-6255 has done some work, this
> jira is to complete this task - support configuring services through REST API
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
