[ https://issues.apache.org/jira/browse/MAPREDUCE-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated MAPREDUCE-1105: ---------------------------------------- Attachment: MAPREDUCE-1105_apache0202.txt This is a back port of this (and likely other capacity changes) from Yahoo! 0.20 to Apache 0.20.2. > CapacityScheduler: It should be possible to set queue hard-limit beyond it's > actual capacity > -------------------------------------------------------------------------------------------- > > Key: MAPREDUCE-1105 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1105 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: contrib/capacity-sched > Affects Versions: 0.21.0 > Reporter: Arun C Murthy > Assignee: rahul k singh > Priority: Blocker > Fix For: 0.21.0 > > Attachments: MAPRED-1105-21-1.patch, MAPRED-1105-21-2.patch, > MAPRED-1105-21-3.patch, MAPRED-1105-21-3.patch, > MAPREDUCE-1105-version20-2.patch, MAPREDUCE-1105-version20.patch.txt, > MAPREDUCE-1105-yahoo-version20-3.patch, > MAPREDUCE-1105-yahoo-version20-4.patch, > MAPREDUCE-1105-yahoo-version20-5.patch, MAPREDUCE-1105_apache0202.txt > > > Currently the CS caps a queue's capacity to it's actual capacity if a > hard-limit is specified to be greater than it's actual capacity. We should > allow the queue to go upto the hard-limit if specified. > Also, I propose we change the hard-limit unit to be percentage rather than > #slots. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.