Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <543521260.1217228371814.JavaMail.jira@brutus>
Date: Sun, 27 Jul 2008 23:59:31 -0700 (PDT)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3842) There is a window where the
 JobTracker is in the RUNNING state (i.e ready to accept jobs) and never
 executes them.
In-Reply-To: <1484225223.1217228251579.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617373#action_12617373 ] 

Amar Kamat commented on HADOOP-3842:
------------------------------------

A simple approach would be to initialize the scheduler early in JobTracker's constructor before making the state {{RUNNING}}.

> 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.