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 "Harsh J (JIRA)" <ji...@apache.org> on 2012/04/21 19:14:34 UTC

[jira] [Updated] (MAPREDUCE-4027) Document the minimum-allocation-mb and maximum-allocation-mb configurations

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

Harsh J updated MAPREDUCE-4027:
-------------------------------

         Description: 
None of the current yarn.scheduler.fifo.minimum/maximum-allocation-mb and yarn.scheduler.capacity.minimum/maximum-allocation-mb are documented anywhere. Without knowledge of these params, one can't change the default allocations. And the default allocations are pretty high btw (MAPREDUCE-4026).

We should document these in the Cluster Setup page at least.

  was:
None of the current yarn.scheduler.fifo.minimum-allocation-mb and yarn.scheduler.capacity.minimum-allocation-mb are documented anywhere. Without knowledge of these params, one can't change the default allocations. And the default allocations are pretty high btw (MAPREDUCE-4026).

We should document these in the Cluster Setup page at least.

    Target Version/s: 2.0.0, trunk  (was: trunk, 2.0.0)
             Summary: Document the minimum-allocation-mb and maximum-allocation-mb configurations  (was: Document the minimum-allocation-mb configurations)
    
> Document the minimum-allocation-mb and maximum-allocation-mb configurations
> ---------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4027
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4027
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 0.23.3
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Minor
>         Attachments: MAPREDUCE-4027.patch, MAPREDUCE-4027.patch
>
>
> None of the current yarn.scheduler.fifo.minimum/maximum-allocation-mb and yarn.scheduler.capacity.minimum/maximum-allocation-mb are documented anywhere. Without knowledge of these params, one can't change the default allocations. And the default allocations are pretty high btw (MAPREDUCE-4026).
> We should document these in the Cluster Setup page at least.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira