[
https://issues.apache.org/jira/browse/MAPREDUCE-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781351#action_12781351
]
rahul k singh commented on MAPREDUCE-1009:
------------------------------------------
cluster_setup.xml
1. In the section conf/mapred-queues.xml .
When we are explaninig the properties we need to specify whether we can change
the value using refresh or not
So we can have 3rd column
can be refreshed.
values being yes , no and Not applicable.
2. Instead of "both from the command line (See this and this)" instead of this
, we can use -list and -info.
3. In section "Refreshing queue configuration" we should mention that no change
is allowed to hierarchy of queues. either in terms of structure or in terms of
name. Only properties are allowed to change.
Instead we are just saying "Not all configuration properties can be reloaded of
course. For example, new queues cannot be added dynamically, neither can an
existing queue be deleted"
capacity_scheduler.xml
1. In section "Configuring Properties for Queues" the table should have
seperate column for refresh as mentioned for cluster_setup.xml
> 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
>
>
> 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.
