[
https://issues.apache.org/jira/browse/YARN-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980693#comment-15980693
]
Jian He commented on YARN-6405:
-------------------------------
Thanks for the explanation,
I fixed the issue by adding failedInstanceName field in ProviderRole. Another
better way may be to use YARN-4879 feature, which uses the
ResourceRequest#getAllocationRequestId to have 1 to 1 mapping from the resource
request to the actual container. I'll do this later.
I also included your uniq-name test in this patch.
bq. Is being able to configure that through the API on the todo list?
Yes, I plan to rewrite some of these with the new features added in yarn, e.g.
anti-affinity, auto-restart, YARN-4879
> 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-6405.yarn-native-services.07.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]
