[
https://issues.apache.org/jira/browse/HADOOP-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617758#action_12617758
]
Amar Kamat commented on HADOOP-3842:
------------------------------------
bq. What are the semantics of submitting jobs to a scheduler that does not
consider itself running?
I think you mean JobTracker. Ideally it should throw state exception. Here, the
JT is responding to the RPCs but since the scheduler is not yet up, it fails to
add to the {{JobInitQueue}}.
> There is a window where the JobTracker is in the RUNNING state (i.e ready to
> accept jobs) and never executes them.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3842
> URL: https://issues.apache.org/jira/browse/HADOOP-3842
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amar Kamat
> Priority: Blocker
>
> Prior to HADOOP-3412, job tracker could accept jobs without even offering
> service (i.e without {{JobTracker.offerService()}} being called). In such a
> case the job stays in JT's memory and job execution was guaranteed. With
> HADOOP-3412, {{JobTracker.submitJob()}} adds the job to JT's local structures
> and passes it to the scheduler. Scheduler gets initialized in
> {{JobTracker.offerService()}} and hence calling {{JobTracker.submitJob()}}
> before calling {{JobTracker.offerService()}} is actually a no-op. The job
> stays in JT's memory but never gets initialized. This is
> - backward incompatible
> - erroneous as there is a window where the jobtracker is ready to accept
> jobs, accepts them and never executes them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
