[
https://issues.apache.org/jira/browse/YARN-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544068#comment-13544068
]
Bikas Saha commented on YARN-314:
---------------------------------
To be clear, I think there is no issue in requesting resources of different
sizes (at same priority and location). Its possible to express that in the
protocol. The issue is that AppSchedulingInfo loses that information by storing
ResourceRequest only by priority and location instead of priority, location and
size.
> Allow resource requests of different sizes at the same priority and locality
> ----------------------------------------------------------------------------
>
> Key: YARN-314
> URL: https://issues.apache.org/jira/browse/YARN-314
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 2.0.2-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Fix For: 2.0.3-alpha
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
