[
https://issues.apache.org/jira/browse/YARN-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza updated YARN-664:
----------------------------
Description: Nothing stops an application from submitting a request with
priority=1, location=*, memory=1024 and a request with priority=1,
location=rack1, memory=2048. 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.
(was: 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.)
> 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=2048. 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
