hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1850) eliminate parameters that must change with cluster size
Date Thu, 06 Sep 2007 20:31:28 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Doug Cutting updated HADOOP-1850:
---------------------------------

    Description: 
As far as possible, configurations should be independent of cluster size.  The cluster size
is a parameter that the system knows and should thus be used to size things accordingly. 
Currently we know that the following parameters must be adjusted to non-default values for
large clusters:
 - mapred.job.tracker.handler.count
 - mapred.reduce.parallel.copies
 - tasktracker.http.threads

We should attempt to make each of these either set to something proportional to cluster size
or (harder) dynamically sized based on load.

  was:
As far as possible, configurations should be independent of cluster size.  The cluster size
is a parameter that the system knows and should thus be used to size things accordingly. 
Currently we know that the following parameters must be adjusted to non-default values for
large clusters:
 - mapred.job.tracker.handler.count
 - mapred.reduce.parallel.copies
 - tasktracker.http.threads
We should attempt to make each of these either set to something proportional to cluster size
or (harder) dynamically sized based on load.


> eliminate parameters that must change with cluster size
> -------------------------------------------------------
>
>                 Key: HADOOP-1850
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1850
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Doug Cutting
>             Fix For: 0.15.0
>
>
> As far as possible, configurations should be independent of cluster size.  The cluster
size is a parameter that the system knows and should thus be used to size things accordingly.
 Currently we know that the following parameters must be adjusted to non-default values for
large clusters:
>  - mapred.job.tracker.handler.count
>  - mapred.reduce.parallel.copies
>  - tasktracker.http.threads
> We should attempt to make each of these either set to something proportional to cluster
size or (harder) dynamically sized based on load.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message