Return-Path: Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: (qmail 53348 invoked from network); 26 Nov 2010 04:40:37 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Nov 2010 04:40:37 -0000 Received: (qmail 17242 invoked by uid 500); 26 Nov 2010 04:40:37 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 17132 invoked by uid 500); 26 Nov 2010 04:40:37 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 17124 invoked by uid 99); 26 Nov 2010 04:40:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Nov 2010 04:40:36 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Nov 2010 04:40:35 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oAQ4eDc9010249 for ; Fri, 26 Nov 2010 04:40:15 GMT Message-ID: <24066347.320631290746413841.JavaMail.jira@thor> Date: Thu, 25 Nov 2010 23:40:13 -0500 (EST) From: "Vinay Kumar Thota (JIRA)" To: mapreduce-issues@hadoop.apache.org Subject: [jira] Updated: (MAPREDUCE-2192) Gridmix tests with MR streaming job traces. In-Reply-To: <30654224.176071290092596237.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay Kumar Thota updated MAPREDUCE-2192: ----------------------------------------- Description: Develop gridmix system tests for below scenarios by using different time interval MR streaming jobs. 1. Generate input data based on cluster size and create the synthetic jobs by using the 2 min folded MR streaming jobs trace and submit the jobs with below arguments. GRIDMIX_JOB_TYPE = LOADJOB GRIDMIX_USER_RESOLVER = SubmitterUserResolver GRIDMIX_SUBMISSION_POLICY = STRESS GRIDMIX_JOB_SUBMISSION_QUEUE_IN_TRACE = True Input Size = 250 MB * No. of nodes in cluster. MINIMUM_FILE_SIZE=150MB TRACE_FILE = 2 min folded trace. Verify JobStatus for each job, input split size for each job and summary (QueueName, UserName, StatTime, FinishTime, maps, reducers and counters etc) after completion of execution. 2. Generate input data based on cluster size and create the synthetic jobs by using the 3 min folded MR streaming jobs trace and submit the jobs with below arguments. GRIDMIX_JOB_TYPE = LoadJob GRIDMIX_USER_RESOLVER = RoundRobinUserResolver GRIDMIX_BYTES_PER_FILE = 150 MB GRIDMIX_SUBMISSION_POLICY = REPLAY GRIDMIX_JOB_SUBMISSION_QUEUE_IN_TRACE = True Input Size = 200 MB * No. of nodes in cluster. PROXY_USERS = proxy users file path TRACE_FILE = 3 min folded trace. Verify JobStatus for each job, input split size for each job and summary (QueueName, UserName, StatTime, FinishTime, maps, reducers and counters etc) after completion of execution. 3. Generate input data based on cluster size and create the synthetic jobs by using the 5 min MR streaming jobs trace and submit the jobs with below arguments. GRIDMIX_JOB_TYPE = LoadJob GRIDMIX_USER_RESOLVER = SubmitterUserResolver GRIDMIX_SUBMISSION_POLICY = SERIAL GRIDMIX_JOB_SUBMISSION_QUEUE_IN_TRACE = false GRIDMIX_KEY_FRC = 0.5f Input Size = 200MB * No. of nodes in cluster. TRACE_FILE = 5 min folded trace. Verify JobStatus for each job and summary (QueueName, UserName, StatTime, FinishTime, MAPS, REDUCERS and COUNTERS etc) after completion of execution. was: 1. Generate input data based on cluster size and create the synthetic jobs by using the 2 min folded MR streaming jobs trace and submit the jobs with below arguments. GRIDMIX_JOB_TYPE = LOADJOB GRIDMIX_USER_RESOLVER = SubmitterUserResolver GRIDMIX_SUBMISSION_POLICY = STRESS GRIDMIX_JOB_SUBMISSION_QUEUE_IN_TRACE = True Input Size = 250 MB * No. of nodes in cluster. MINIMUM_FILE_SIZE=150MB TRACE_FILE = 2 min folded trace. Verify JobStatus for each job, input split size for each job and summary (QueueName, UserName, StatTime, FinishTime, maps, reducers and counters etc) after completion of execution. 2. Generate input data based on cluster size and create the synthetic jobs by using the 3 min folded MR streaming jobs trace and submit the jobs with below arguments. GRIDMIX_JOB_TYPE = LoadJob GRIDMIX_USER_RESOLVER = RoundRobinUserResolver GRIDMIX_BYTES_PER_FILE = 150 MB GRIDMIX_SUBMISSION_POLICY = REPLAY GRIDMIX_JOB_SUBMISSION_QUEUE_IN_TRACE = True BYTES_PER_FILE = 200 MB Input Size = 250 MB * No. of nodes in cluster. PROXY_USERS = proxy users file path TRACE_FILE = 3 min folded trace. Verify JobStatus for each job, input split size for each job and summary (QueueName, UserName, StatTime, FinishTime, maps, reducers and counters etc) after completion of execution. 3. Generate input data based on cluster size and create the synthetic jobs by using the 5 min MR streaming jobs trace and submit the jobs with below arguments. GRIDMIX_JOB_TYPE = LoadJob GRIDMIX_USER_RESOLVER = SubmitterUserResolver GRIDMIX_SUBMISSION_POLICY = SERIAL GRIDMIX_JOB_SUBMISSION_QUEUE_IN_TRACE = false Input Size = 200MB * No. of nodes in cluster. TRACE_FILE = 5 min folded trace. Verify JobStatus for each job and summary (QueueName, UserName, StatTime, FinishTime, MAPS, REDUCERS and COUNTERS etc) after completion of execution. Summary: Gridmix tests with MR streaming job traces. (was: Gridmix tests for MR streaming job traces.) > Gridmix tests with MR streaming job traces. > ------------------------------------------- > > Key: MAPREDUCE-2192 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2192 > Project: Hadoop Map/Reduce > Issue Type: Task > Components: contrib/gridmix > Reporter: Vinay Kumar Thota > Assignee: Vinay Kumar Thota > Attachments: MAPREDUCE-2192.patch > > > Develop gridmix system tests for below scenarios by using different time interval MR streaming jobs. > 1. Generate input data based on cluster size and create the synthetic jobs by using the 2 min folded MR streaming jobs trace and submit the jobs with below arguments. > GRIDMIX_JOB_TYPE = LOADJOB > GRIDMIX_USER_RESOLVER = SubmitterUserResolver > GRIDMIX_SUBMISSION_POLICY = STRESS > GRIDMIX_JOB_SUBMISSION_QUEUE_IN_TRACE = True > Input Size = 250 MB * No. of nodes in cluster. > MINIMUM_FILE_SIZE=150MB > TRACE_FILE = 2 min folded trace. > Verify JobStatus for each job, input split size for each job and summary (QueueName, UserName, StatTime, FinishTime, maps, reducers and counters etc) after completion of execution. > 2. Generate input data based on cluster size and create the synthetic jobs by using the 3 min folded MR streaming jobs trace and submit the jobs with below arguments. > GRIDMIX_JOB_TYPE = LoadJob > GRIDMIX_USER_RESOLVER = RoundRobinUserResolver > GRIDMIX_BYTES_PER_FILE = 150 MB > GRIDMIX_SUBMISSION_POLICY = REPLAY > GRIDMIX_JOB_SUBMISSION_QUEUE_IN_TRACE = True > Input Size = 200 MB * No. of nodes in cluster. > PROXY_USERS = proxy users file path > TRACE_FILE = 3 min folded trace. > Verify JobStatus for each job, input split size for each job and summary (QueueName, UserName, StatTime, FinishTime, maps, reducers and counters etc) after completion of execution. > 3. Generate input data based on cluster size and create the synthetic jobs by using the 5 min MR streaming jobs trace and submit the jobs with below arguments. > GRIDMIX_JOB_TYPE = LoadJob > GRIDMIX_USER_RESOLVER = SubmitterUserResolver > GRIDMIX_SUBMISSION_POLICY = SERIAL > GRIDMIX_JOB_SUBMISSION_QUEUE_IN_TRACE = false > GRIDMIX_KEY_FRC = 0.5f > Input Size = 200MB * No. of nodes in cluster. > TRACE_FILE = 5 min folded trace. > Verify JobStatus for each job and summary (QueueName, UserName, StatTime, FinishTime, MAPS, REDUCERS and COUNTERS etc) after completion of execution. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.