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 "David Ginzburg (Commented) (JIRA)" <ji...@apache.org> on 2012/01/18 10:35:39 UTC
[jira] [Commented] (MAPREDUCE-2638) Create a simple stress test for
the fair scheduler
[ https://issues.apache.org/jira/browse/MAPREDUCE-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188357#comment-13188357 ]
David Ginzburg commented on MAPREDUCE-2638:
-------------------------------------------
I'm not sure this is related to this issue, but I suspect preemption causes
Inconsistent result when fairscheduler preemption is on.
I have reported it at http://mail-archives.apache.org/mod_mbox/hadoop-mapreduce-user/201201.mbox/%3CSNT135-W231F0B5F0D6A3AE0A5EDC9B79F0@phx.gbl%3E
Maybe this stress test can help reproduce it easily, on clusters other than the one I'm running.
> Create a simple stress test for the fair scheduler
> --------------------------------------------------
>
> Key: MAPREDUCE-2638
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2638
> Project: Hadoop Map/Reduce
> Issue Type: Test
> Components: contrib/fair-share
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.24.0
>
> Attachments: MAPREDUCE-2638.patch, MAPREDUCE-2638.patch
>
>
> This would be a test that runs against a cluster, typically with settings that allow preemption to be exercised.
--
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