You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2007/07/20 07:16:06 UTC
[jira] Commented: (HADOOP-1636) constant should be
user-configurable: MAX_COMPLETE_USER_JOBS_IN_MEMORY
[ https://issues.apache.org/jira/browse/HADOOP-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514096 ]
Hadoop QA commented on HADOOP-1636:
-----------------------------------
+1
http://issues.apache.org/jira/secure/attachment/12362190/configure-max-completed-jobs.patch applied and successfully tested against trunk revision r557790.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/440/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/440/console
> constant should be user-configurable: MAX_COMPLETE_USER_JOBS_IN_MEMORY
> ----------------------------------------------------------------------
>
> Key: HADOOP-1636
> URL: https://issues.apache.org/jira/browse/HADOOP-1636
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.13.0
> Reporter: Michael Bieniosek
> Attachments: configure-max-completed-jobs.patch
>
>
> In JobTracker.java: static final int MAX_COMPLETE_USER_JOBS_IN_MEMORY = 100;
> This should be configurable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.