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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/05/02 06:36:07 UTC
[jira] [Commented] (MAPREDUCE-5704) Optimize nextJobId in
JobTracker
[ https://issues.apache.org/jira/browse/MAPREDUCE-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524744#comment-14524744 ]
Hadoop QA commented on MAPREDUCE-5704:
--------------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12621052/MAPREDUCE-5704.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5535/console |
This message was automatically generated.
> Optimize nextJobId in JobTracker
> --------------------------------
>
> Key: MAPREDUCE-5704
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5704
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker, mrv1
> Affects Versions: 1.2.1
> Reporter: JamesLi
> Assignee: JamesLi
> Attachments: MAPREDUCE-5704.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)