[
https://issues.apache.org/jira/browse/HADOOP-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632659#action_12632659
]
Steve Loughran commented on HADOOP-3245:
----------------------------------------
I am finding the new TestJobTrackerRestart* tests take a very long time to run
on my machine, upward of 10 minutes...if I'm doing anything else on the system
at the same time the tests time out and get killed.
-how long does the test run take for other people on their desktop?
-there's a lot of waits for a minute or more -are these really needed? Could
more polling for the job tracker to be unreachable be used as a metric, or
asking the task tracker if they are still live?
if thes test does take a long time, is it possible to somehow group this into
the 'slow test' category; otherwise my test cycle has just been extended by 50%.
> Provide ability to persist running jobs (extend HADOOP-1876)
> ------------------------------------------------------------
>
> Key: HADOOP-3245
> URL: https://issues.apache.org/jira/browse/HADOOP-3245
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Reporter: Devaraj Das
> Assignee: Amar Kamat
> Fix For: 0.19.0
>
> Attachments: HADOOP-3245-v2.5.patch, HADOOP-3245-v2.6.5.patch,
> HADOOP-3245-v2.6.9.patch, HADOOP-3245-v4.1.patch, HADOOP-3245-v5.13.patch,
> HADOOP-3245-v5.14.patch, HADOOP-3245-v5.26.patch,
> HADOOP-3245-v5.30-nolog.patch, HADOOP-3245-v5.31.3-nolog.patch,
> HADOOP-3245-v5.33.1.patch, HADOOP-3245-v5.35.3-no-log.patch,
> HADOOP-3245-v5.36-no-log.patch, HADOOP-3245-v5.36.1-no-log.patch,
> HADOOP-3245-v5.36.2-no-log.patch, HADOOP-3245-v5.36.3-no-log.patch,
> HADOOP-3245-v5.36.3-no-log.patch
>
>
> This could probably extend the work done in HADOOP-1876. This feature can be
> applied for things like jobs being able to survive jobtracker restarts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
