[
https://issues.apache.org/jira/browse/MAPREDUCE-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411754#comment-13411754
]
Karthik Kambatla commented on MAPREDUCE-4299:
---------------------------------------------
Tom,
Thanks for the patch.
I had a couple of questions though, please correct me if I understand it wrong.
- Just realized that the application headroom is being set after the for loop;
shouldn't we update it within the for loop itself so that subsequent iterations
(applications) would see the updated resources.
- If number of applications makes a difference, the test should probably have
more applications before we trigger node update.
> Terasort hangs with MR2 FifoScheduler
> -------------------------------------
>
> Key: MAPREDUCE-4299
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4299
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha
> Reporter: Tom White
> Assignee: Tom White
> Attachments: MAPREDUCE-4299.patch, MAPREDUCE-4299.patch
>
>
> What happens is that the number of reducers ramp up until they occupy all of
> the job's containers, at which point the maps no longer make any progress and
> the job hangs.
> When the same job is run with the CapacityScheduler it succeeds, so this
> looks like a FifoScheduler bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
