Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 21 Nov 2011 04:11:52 +0000 (UTC)
From: "Amar Kamat (Created) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <23500872.50122.1321848712049.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (MAPREDUCE-3439) [Gridmix] Support addons in
 Gridmix
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

[Gridmix] Support addons in Gridmix
-----------------------------------

                 Key: MAPREDUCE-3439
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3439
             Project: Hadoop Map/Reduce
          Issue Type: New Feature
          Components: contrib/gridmix
    Affects Versions: 0.24.0
            Reporter: Amar Kamat
            Assignee: Amar Kamat
             Fix For: 0.24.0


At times there is a need to benchmark certain Hadoop client APIs. Often, this is done by running simple & standard sort-like programs on Hadoop and then using an external utility to benchmark the APIs. But then the benchmarking results tend to be off from reality as the load on the cluster doesn't match the actual load. We believe that Gridmix3 - which is a Hadoop workload simulator - can prove useful here. Gridmix3 already provides a mechanism to load the cluster - often called as a 'test cluster' - using a real trace thus mimicking the real-life workload.

Currently, Gridmix3 consumes a representative workload trace and loads the Hadoop cluster to match what is seen in the trace. Gridmix3 can be enhanced to also support user scripts (hereby referred as 'addons') which will be loaded within Gridmix3 and will get updates like
1. Job submission
2. Job completion
3. Cluster status

These addons can also ping/access a live, close-to-real-life Hadoop cluster. This will allow users to benchmark the Hadoop cluster while it is running. 

--
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