You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Sandy Ryza (JIRA)" <ji...@apache.org> on 2013/05/10 23:25:16 UTC

[jira] [Created] (YARN-664) throw InvalidRequestException for requests with different capabilities at the same priority

Sandy Ryza created YARN-664:
-------------------------------

             Summary: 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