[
https://issues.apache.org/jira/browse/MAPREDUCE-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934817#action_12934817
]
Vinay Kumar Thota commented on MAPREDUCE-2138:
----------------------------------------------
bq. jobstories looks like the same map as zombieJobs, as far as I can tell, and
therefore redundant. (I had the same comment for the previous version of this
patch.)
Sorry, some how i had missed the modified code in the patch. Now re-generated
the patch with updated code.
bq. GridmixJobVerification.convertToSecs() seems to have a bug - it should
divide by 10^9 not 10^10 when converting from nano-seconds to seconds.
done. Changed the code.
bq. For a neat version of GridmixJobVerification.convertBytes(), check out
aioobe's answer on Stack Overflow.
Modified the method.
bq. What does OVERALL mean as a job-status in
GridmixJobVerification.convertJobStatus()?
Changed the method. As per one of the Rumen class(HadoopLogsAnalyzer), it shows
OVERALL in the trace, if neither job is succeed or failed. But I have changed
the method based on new code in ZombieJob.
bq. In GridmixJobVerification.getCounterValue(), shouldn't you be using the
actual name of the counter rather than the display-name? The display-name is
liable to change according to the whim of the developers. (Of course, the
callers will also have to change accordingly.)
Done. Changed the code.
> Gridmix tests with different time interval mr traces (1min, 3min and 5min).
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-2138
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2138
> Project: Hadoop Map/Reduce
> Issue Type: Task
> Components: test
> Reporter: Vinay Kumar Thota
> Assignee: Vinay Kumar Thota
> Attachments: MAPREDUCE-2138.patch, MAPREDUCE-2138.patch,
> MAPREDUCE-2138.patch
>
>
> 1. Generate input data based on cluster size and create the synthetic jobs by
> using the 1 min folded MR trace and
> submit the jobs with below arguments.
> GRIDMIX_JOB_TYPE = LoadJob
> GRIDMIX_USER_RESOLVER = SubmitterUserResolver
> GRIDMIX_SUBMISSION_POLICY = STRESS
> Input Size = 400 MB * No. of nodes in cluster.
> TRACE_FILE = 1 min folded trace.
> Verify each job status 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 trace and
> submit the jobs with below arguments.
> GRIDMIX_JOB_TYPE = LoadJob
> GRIDMIX_USER_RESOLVER = RoundRobinUserResolver
> GRIDMIX_SUBMISSION_POLICY = Replay
> Input Size = 200 MB * No. of nodes in cluster.
> TRACE_FILE = 3 min folded trace.
> PROXY_USERS = proxy users file path.
> Verify each job status, submitted user 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 folded MR trace and
> submit the jobs with below arguments.
> GRIDMIX_JOB_TYPE = SleepJob
> GRIDMIX_USER_RESOLVER = EchoUserResolver
> GRIDMIX_MIN_FILE = 100 MB
> GRIDMIX_SUBMISSION_POLICY = Serial
> Input Size = 300 MB * No. of nodes in cluster.
> TRACE_FILE = 5 min folded trace.
> Verify each job status, file size 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.
