Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-5704

Optimize nextJobId in JobTracker

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Patch Available
    • Major
    • Resolution: Unresolved
    • 1.2.1
    • None
    • jobtracker, mrv1

    Description

      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.
      In jobhistory_jsp.java, array SCAN_SIZES controls job numbers displayed on jobhistory.jsp.
      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.

      Attachments

        1. MAPREDUCE-5704.patch
          6 kB
          JamesLi

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            hbjoylee JamesLi
            hbjoylee JamesLi

            Dates

              Created:
              Updated:

              Slack

                Issue deployment