You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Brahma Reddy Battula (JIRA)" <ji...@apache.org> on 2016/02/08 06:02:40 UTC
[jira] [Created] (MAPREDUCE-6629) Cluster used capacity is > 100
when container reserved
Brahma Reddy Battula created MAPREDUCE-6629:
-----------------------------------------------
Summary: Cluster used capacity is > 100 when container reserved
Key: MAPREDUCE-6629
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6629
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Brahma Reddy Battula
Assignee: Brahma Reddy Battula
*Scenario:*
* Start cluster with Three NM's each having 8GB (cluster memory:24GB).
* Configure queues with elasticity and userlimitfactor=10.
* disable pre-emption.
* run two job with different priority in different queue at the same time
** yarn jar hadoop-mapreduce-examples-2.7.2.jar pi -Dyarn.app.priority=LOW -Dmapreduce.job.queuename=QueueA -Dmapreduce.map.memory.mb=4096 -Dyarn.app.mapreduce.am.resource.mb=1536 -Dmapreduce.job.reduce.slowstart.completedmaps=1.0 10 1000000000000
** yarn jar hadoop-mapreduce-examples-2.7.2.jar pi -Dyarn.app.priority=HIGH -Dmapreduce.job.queuename=QueueB -Dmapreduce.map.memory.mb=4096 -Dyarn.app.mapreduce.am.resource.mb=1536 3 1000000000000
* observe the cluster capacity which was used in RM web UI
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)