You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/22 22:30:40 UTC

[jira] [Resolved] (MAPREDUCE-352) Avoid creating JobInProgress objects before Access checks and Queues checks are done in JobTracker submitJob

     [ https://issues.apache.org/jira/browse/MAPREDUCE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-352.
----------------------------------------

    Resolution: Incomplete

Stale with YAWN.  I mean YARN.

> Avoid creating JobInProgress objects before Access checks and Queues checks are done in JobTracker submitJob 
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-352
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-352
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            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 was sent by Atlassian JIRA
(v6.2#6252)