[
https://issues.apache.org/jira/browse/YARN-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564274#comment-14564274
]
Xianyin Xin commented on YARN-314:
----------------------------------
How about use a form to organize the request, just like we usually fill many
application forms in daily life? The form has an unique ID which stands for a
specific request. With the form, we needn't refresh the request with the same
priority and location submitted through previous heartbeat, but treated them as
different requests as long as they have different form ID. An app could submit
many forms, in which request with specific priority, location, capacity could
be raised. The form could be created by AM, and then passed to scheduler, after
allocate all the containers, this form is fulfilled. A form is a singleton,
could be created, fulfilled and revoked(or destroyed).
In fact, now the scheduler refresh and update the request may cause temporary
inconsistent between the resource request declared by AM and that record by
scheduler, see YARN-3558, and form is a nice solution, i think. That's another
thing.
> Schedulers should allow resource requests of different sizes at the same
> priority and location
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-314
> URL: https://issues.apache.org/jira/browse/YARN-314
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: scheduler
> Affects Versions: 2.0.2-alpha
> Reporter: Sandy Ryza
> Assignee: Karthik Kambatla
> Attachments: yarn-314-prelim.patch
>
>
> Currently, resource requests for the same container and locality are expected
> to all be the same size.
> While it it doesn't look like it's needed for apps currently, and can be
> circumvented by specifying different priorities if absolutely necessary, it
> seems to me that the ability to request containers with different resource
> requirements at the same priority level should be there for the future and
> for completeness sake.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
