[
https://issues.apache.org/jira/browse/YARN-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654986#comment-13654986
]
Hitesh Shah commented on YARN-664:
----------------------------------
Original comment still holds for an AM being able to request 1 container of 1
GB and 1 container of 4 GB both at priority 1.
> throw InvalidRequestException for requests with different capabilities at the
> same priority
> -------------------------------------------------------------------------------------------
>
> Key: YARN-664
> URL: https://issues.apache.org/jira/browse/YARN-664
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager, scheduler
> Affects Versions: 2.0.4-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
>
> Nothing stops an application from submitting a request with priority=1,
> location=*, memory=1024 and a request with priority=1, location=rack1,
> memory=1024. However, this does not make sense under the request model and
> can cause bad things to happen in the scheduler. It should be possible to
> detect this at AMRM heartbeat time and throw an exception.
--
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
