hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1451) A couple tests rely on the capacity scheduler
Date Tue, 26 Nov 2013 21:53:35 GMT

     [ https://issues.apache.org/jira/browse/YARN-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sandy Ryza updated YARN-1451:
-----------------------------

    Description: 
TestNetworkedJob and TestResourceManager rely on the capacity scheduler.

For TestNetworkedJob, the queue name chosen for the job is different for the Fair Scheduler.
 Configuring the Capacity Scheduler explicitly would make this dependency more clear.

TestResourceManager relies on a scheduler that assigns multiple containers in a single heartbeat,
which not all schedulers do by default.  It also relies on schedulers that don't consider
CPU capacities.  It would be simple to change the test to use multiple heartbeats increase
the vcore capacities of the nodes in the test.

  was:
TestNetworkedJob and TestResourceManager rely on the capacity scheduler.

For TestNetworkedJob, the queue name chosen for the job is different for the Fair Scheduler.
 Configuring the Capacity Scheduler explicitly would make this dependency more clear.

TestResourceManager relies on a scheduler that assigns multiple containers in a single heartbeat,
which not all schedulers do by default.  It would be simple to change the test to use multiple
heartbeats.


> A couple tests rely on the capacity scheduler
> ---------------------------------------------
>
>                 Key: YARN-1451
>                 URL: https://issues.apache.org/jira/browse/YARN-1451
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>            Priority: Minor
>
> TestNetworkedJob and TestResourceManager rely on the capacity scheduler.
> For TestNetworkedJob, the queue name chosen for the job is different for the Fair Scheduler.
 Configuring the Capacity Scheduler explicitly would make this dependency more clear.
> TestResourceManager relies on a scheduler that assigns multiple containers in a single
heartbeat, which not all schedulers do by default.  It also relies on schedulers that don't
consider CPU capacities.  It would be simple to change the test to use multiple heartbeats
increase the vcore capacities of the nodes in the test.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message