hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-1261) Enhance mumak to implement a 'stress-test' for the JobTracker
Date Tue, 29 Jul 2014 21:00:39 GMT

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

Allen Wittenauer resolved MAPREDUCE-1261.

    Resolution: Won't Fix

> Enhance mumak to implement a 'stress-test' for the JobTracker
> -------------------------------------------------------------
>                 Key: MAPREDUCE-1261
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1261
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: contrib/mumak
>            Reporter: Arun C Murthy
> I propose we enhance mumak to implement a proper 'stress-test' tool for the JobTracker.
The idea is that we enhance mumak to have a mode where it can use the *real* JobTracker (and
Scheduler of course) and mumak's SimulatedTaskTracker to run real workloads from production
job-history traces. Clearly we will need to make necessary changes to allow the SimulatedTaskTrackers
to run independently (a thread per SimulatedTT) in a distributed manner.
> We can then simulate very large clusters and workloads using a handful of machines (say
~50 machines to simulate workload which originally ran on a 4000 node cluster), also we can
use this to stress the JobTracker with synthetic workloads.
> Thoughts?

This message was sent by Atlassian JIRA

View raw message