[
https://issues.apache.org/jira/browse/HADOOP-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-3245:
-------------------------------
Attachment: HADOOP-3245-v2.6.9.patch
Had an offline discussion with Devaraj. Attaching a patch that includes his
comments.
1) Remove some security checks since HADOOP-3578 should take care of that.
2) Remove the _queued_ concept since HADOOP-3444 should take care of that.
As mentioned earlier, the job runtime will be useless once the JT restarts as
the job could be running for more time than the time displayed. There are some
ways in which this problem can be solved but looks like it might require some
more work. We think that the problem of job-runtime, job-priority and
job-kill/task-kill can be handled in a separate issue. With this patch we will
show the new job runtime as 0 indicating that the job runtime is unknown.
> 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
> Attachments: HADOOP-3245-v2.5.patch, HADOOP-3245-v2.6.5.patch,
> HADOOP-3245-v2.6.9.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.
