hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1009) Forrest documentation needs to be updated to describes features provided for supporting hierarchical queues
Date Thu, 10 Dec 2009 10:04:18 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788637#action_12788637
] 

Hemanth Yamijala commented on MAPREDUCE-1009:
---------------------------------------------

A few comments on this patch:

- Why is the docs target copying xml template files to build ? In case it is needed, shouldn't
the target be overridden in capacity-scheduler's build file, rather than putting contrib specific
operations in build.xml.
- The documentation of maximum-capacity in capacity-scheduler's mapred-queues.xml.template
seems to have problems. E.g. it says: maximum-capacity-stretch instead of maximum-capacity.
Mentions default value as 100. It also talks about sub-queues, but that becomes ambiguous
if this is a leaf queue. Same applies for Forrest documentation.
- Maybe we should specify in the conf template file and the forrest documentation what properties
apply for container queues and what don't.
- In the example (using queues q1 and q2) can we scrub the values of properties to be more
clear - like we have capacity set to 0, which is wrong.
- The link to conf/mapred-queues.xml.template in cluster_setup.xml seems wrong. It is pointing
t mapred-queues.xml and not the template.
- Typo: But the usage of multiple as well as hierarchical queues in actually dependent...
-> should be ...hierarchical queues is actually dependent...
- I think it makes sense to explicitly define what hierarchical queues are somewhere early
on when talking about queues. What they are, how they can be used etc. Because we refer to
it at multiple places but I don't think the intent is explicitly coming out.
- Queue refresh is also a scheduler specific supported feature. Should we call that out in
the cluster-setup documentation ?
- I think we need not mention that queue web UI uses YUI. It seems like an implementation
detail. Any specific reason for mentioning this ?
- Shouldn't the Map/Reduce commands section move to the commands manual ? And we can possibly
link them from cluster-setup. There seems to be a specific format we are using for describing
the commands and it would be consistent to mention it in the same way, which we can easily
do by moving to the commands manual.

> Forrest documentation needs to be updated to describes features provided for supporting
hierarchical queues
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1009
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1009
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.21.0
>            Reporter: Hemanth Yamijala
>            Assignee: Vinod K V
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: MAPREDUCE-1009-20091008.txt, MAPREDUCE-1009-20091116.txt, MAPREDUCE-1009-20091124.txt
>
>
> Forrest documentation must be updated for describing how to set up and use hierarchical
queues in the framework and the capacity scheduler.

-- 
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