[
https://issues.apache.org/jira/browse/MAPREDUCE-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874502#action_12874502
]
Amar Kamat commented on MAPREDUCE-1833:
---------------------------------------
Two comments
1) Shouldn't we keep GridMix.java (i.e GridMix command line params) independent
of the synthetic job's (in this case SleepJob) config parameters?
2) Should we name the config parameter as gridmix.job.sleepjob.reduce.max-time
instead of gridmix.job.sleepjob.reduce.max-time? This will allow us to put
common job level configs under gridmix.job.* and a specific synthetic job level
config under gridmix.job.jobname.*
> [gridmix3] limit the maximum task duration in sleep job.
> --------------------------------------------------------
>
> Key: MAPREDUCE-1833
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1833
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/gridmix
> Reporter: Hong Tang
> Attachments: mr-1833-yahoo-20.10.patch, mr-1833-yahoo-20.1xx.patch
>
>
> In production job history logs, sometimes a task takes very long time to
> finish. Replaying such trace in sleep-job mode in Gridmix3 would
> unnecessarily prolong the benchmark execution time. It would be desirable to
> allow users to limit the maximum task duration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
