[MAPREDUCE-728] Mumak: Map-Reduce Simulator

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.21.0
• Fix Version/s: 0.21.0
• Hadoop Flags: Reviewed
• Assignee: Hong Tang
• Reporter: Arun Murthy
• Created: 07/Jul/09 21:45
• Updated: 30/Oct/15 10:28
• Resolved: 25/Sep/09 00:26

Description

Vision:

We want to build a Simulator to simulate large-scale Hadoop clusters, applications and workloads. This would be invaluable in furthering Hadoop by providing a tool for researchers and developers to prototype features (e.g. pluggable block-placement for HDFS, Map-Reduce schedulers etc.) and predict their behaviour and performance with reasonable amount of confidence, there-by aiding rapid innovation.

---

First Cut: Simulator for the Map-Reduce Scheduler

The Map-Reduce Scheduler is a fertile area of interest with at least four schedulers, each with their own set of features, currently in existence: Default Scheduler, Capacity Scheduler, Fairshare Scheduler & Priority Scheduler.

Each scheduler's scheduling decisions are driven by many factors, such as fairness, capacity guarantee, resource availability, data-locality etc.

Given that, it is non-trivial to accurately choose a single scheduler or even a set of desired features to predict the right scheduler (or features) for a given workload. Hence a simulator which can predict how well a particular scheduler works for some specific workload by quickly iterating over schedulers and/or scheduler features would be quite useful.

So, the first cut is to implement a simulator for the Map-Reduce scheduler which take as input a job trace derived from production workload and a cluster definition, and simulates the execution of the jobs in as defined in the trace in this virtual cluster. As output, the detailed job execution trace (recorded in relation to virtual simulated time) could then be analyzed to understand various traits of individual schedulers (individual jobs turn around time, throughput, faireness, capacity guarantee, etc). To support this, we would need a simulator which could accurately model the conditions of the actual system which would affect a schedulers decisions. These include very large-scale clusters (thousands of nodes), the detailed characteristics of the workload thrown at the clusters, job or task failures, data locality, and cluster hardware (cpu, memory, disk i/o, network i/o, network topology) etc.

Issue Links

• is blocked by: MAPREDUCE-995 JobHistory should handle cases where task completion events are generated after job completion event
• is blocked by: MAPREDUCE-751 Rumen: a tool to extract job characterization data from job tracker logs
• is cloned by: MAPREDUCE-6531 CLONE - Mumak: Map-Reduce Simulator
• relates to: MAPREDUCE-1001 Reducing code duplication in Mumak
• relates to: MAPREDUCE-1006 Making JobStoryProducer and ClusterStory pluggable in Mumak
• relates to: MAPREDUCE-729 Create a MapReduceMaster interface for the JobTracker

Sub-Tasks

• Create Fake Log from Hadoop: Open