hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5977) Avoid creating JobInProgress objects before Access checks and Queues checks are done in JobTracker submitJob
Date Fri, 05 Jun 2009 10:54:07 GMT

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

Amar Kamat commented on HADOOP-5977:
------------------------------------

Rahul, this is done because the jobconf is loaded in the jip constructor. HADOOP-3578 will
change this as conf will be passed over the rpc.
But in either case +1.

> Avoid creating JobInProgress objects before Access checks and Queues checks are done
in JobTracker submitJob 
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5977
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5977
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: rahul k singh
>
> In JobTracker submitJob , JobInProgress instance gets created . after this checks are
done for access and queue state. In event of checks failed . There isn't any use for these
JIP objects , hence in event of failure only reason these objects were created was to get
conf data and be deleted.
> We need to fetch the information required to only do the checks instead of creating a
JobInProgress object

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message