hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantinos Karanasos (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5478) [YARN-4902] Define Java API for generalized & unified scheduling-strategies.
Date Thu, 30 Mar 2017 05:47:45 GMT

    [ https://issues.apache.org/jira/browse/YARN-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948454#comment-15948454

Konstantinos Karanasos commented on YARN-5478:

Hi [~leftnoteasy], 
bq. I think now we generally agree that we should stop investing on the old ResourceRequest
and we should move APIs for new features like Allocation tag, Affinity/Anti-affinity, Node
attributes: YARN-4902, to the new ResourceRequest.
My understanding was that allocation tags that are attached to containers could indeed be
added either in the existing ResourceRequest, in the new ResourceRequest or in the AllocateRequest
object as a map between AllocateRequestID and tags.
For the remaining features (affinity, node attributes), I am still not sure there is need
to add them at the (old or new) ResourceRequest object. It seems that adding constraint expressions
in the ApplicationSubmissionContext and the AllocateRequest (for more targeted ones) is sufficient
for all the use cases we have come across and those mentioned in YARN-4793.

I just uploaded a design document in YARN-5468, where we give more details on our thoughts.
We tried to address all the points we discussed in our last meeting.
Please give it a look and let's continue the discussion.

[~Naganarasimha], please also check the document. Based on our latest discussions with Wangda,
we included a way to specify node attributes in the constraint expression (using namespaces
to differentiate between different type of constraints).

> [YARN-4902] Define Java API for generalized & unified scheduling-strategies.
> ----------------------------------------------------------------------------
>                 Key: YARN-5478
>                 URL: https://issues.apache.org/jira/browse/YARN-5478
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: YARN-5478.1.patch, YARN-5478.2.patch, YARN-5478.preliminary-poc.1.patch,
> Define Java API for application to specify generic scheduling requirements described
in YARN-4902 design doc.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message