hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "JamesLi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-5704) Optimize nextJobId in JobTracker
Date Thu, 02 Jan 2014 09:38:50 GMT
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

View raw message