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 "JamesLi (JIRA)" <ji...@apache.org> on 2014/01/02 10:38:50 UTC

[jira] [Created] (MAPREDUCE-5704) Optimize nextJobId in JobTracker

JamesLi created MAPREDUCE-5704:
----------------------------------

             Summary: Optimize nextJobId in JobTracker
                 Key: MAPREDUCE-5704
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5704
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
    Affects Versions: 1.2.1
            Reporter: JamesLi
            Assignee: JamesLi


When jobtracker start, nextJobId start with 1,if we have run 3000 jobs  then restart jobtracker and run a new job,we can not see this new job on jobtracker:5030/jobhistory.jsp unless click "get more results" button.

I make a little chage,when jobtracker start,find the biggest id under history done directory,job will start with maxId+1 or 1 if can not find any job files.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)