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 "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2008/10/01 05:57:44 UTC
[jira] Created: (HADOOP-4321) Document the capacity scheduler in
Forrest
Document the capacity scheduler in Forrest
------------------------------------------
Key: HADOOP-4321
URL: https://issues.apache.org/jira/browse/HADOOP-4321
Project: Hadoop Core
Issue Type: Bug
Components: contrib/capacity-sched, documentation
Affects Versions: 0.19.0
Reporter: Hemanth Yamijala
Assignee: Hemanth Yamijala
Priority: Blocker
Fix For: 0.19.0
Document the capacity scheduler and related issues, some of which have touched the framework as well. The issues are all linked in HADOOP-3444.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4321) Document the capacity scheduler in
Forrest
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala updated HADOOP-4321:
-------------------------------------
Attachment: HADOOP-4321.patch
The attached patch makes following changes:
- Makes the documentation of the capacity scheduler more complete.
- Links capacity scheduler of the site documentation, so that documentation is actually generated.
- Introduces changes related to setting up queues, ACLs into cluster setup and map/reduce tutorial. These are referenced off the capacity scheduler documentation.
> Document the capacity scheduler in Forrest
> ------------------------------------------
>
> Key: HADOOP-4321
> URL: https://issues.apache.org/jira/browse/HADOOP-4321
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched, documentation
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: 4321.0.patch, HADOOP-4321.patch
>
>
> Document the capacity scheduler and related issues, some of which have touched the framework as well. The issues are all linked in HADOOP-3444.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4321) Document the capacity scheduler in
Forrest
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala updated HADOOP-4321:
-------------------------------------
Status: Patch Available (was: Open)
> Document the capacity scheduler in Forrest
> ------------------------------------------
>
> Key: HADOOP-4321
> URL: https://issues.apache.org/jira/browse/HADOOP-4321
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched, documentation
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: 4321.0.patch, HADOOP-4321.patch
>
>
> Document the capacity scheduler and related issues, some of which have touched the framework as well. The issues are all linked in HADOOP-3444.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4321) Document the capacity scheduler in
Forrest
Posted by "Vivek Ratan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640996#action_12640996 ]
Vivek Ratan commented on HADOOP-4321:
-------------------------------------
Looks good. Some minor comments:
* In 'mapred_tutorial.xml', under 'Submitting Jobs to a Queue', you have the following: "Note that administrators may ... to allowed queues." The wording can be changed a bit. It is not _mandatory_ to submit a job to an allowed queue. A user could submit a job to any queue, but if ACLs are enabled and the user is not allowed to submit jobs to the queue, their job is rejected.
* In 'cluster_setup.xml', under 'mapred.queue.names', you write: "If the scheduler does not support queues, the value of this parameter should be left as _default_." Shouldn't you say something like "the system, and hence any scheduler, always supports at least one queue called _default_, and so this parameter's value should always contain the string 'default'"?
> Document the capacity scheduler in Forrest
> ------------------------------------------
>
> Key: HADOOP-4321
> URL: https://issues.apache.org/jira/browse/HADOOP-4321
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched, documentation
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: 4321.0.patch, HADOOP-4321.patch
>
>
> Document the capacity scheduler and related issues, some of which have touched the framework as well. The issues are all linked in HADOOP-3444.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4321) Document the capacity scheduler in
Forrest
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642298#action_12642298 ]
Hudson commented on HADOOP-4321:
--------------------------------
Integrated in Hadoop-trunk #640 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/640/])
> Document the capacity scheduler in Forrest
> ------------------------------------------
>
> Key: HADOOP-4321
> URL: https://issues.apache.org/jira/browse/HADOOP-4321
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched, documentation
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: 4321.0.patch, HADOOP-4321.patch, HADOOP-4321.patch
>
>
> Document the capacity scheduler and related issues, some of which have touched the framework as well. The issues are all linked in HADOOP-3444.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4321) Document the capacity scheduler in
Forrest
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640922#action_12640922 ]
Hemanth Yamijala commented on HADOOP-4321:
------------------------------------------
Results of test-patch:
[exec] -1 overall.
[exec] +1 @author. The patch does not contain any @author tags.
[exec] -1 tests included. The patch doesn't appear to include any new or modified tests.
[exec] Please justify why no tests are needed for this patch.
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec] +1 findbugs. The patch does not introduce any new Findbugs warnings.
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
There are no tests as it is a documentation patch.
> Document the capacity scheduler in Forrest
> ------------------------------------------
>
> Key: HADOOP-4321
> URL: https://issues.apache.org/jira/browse/HADOOP-4321
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched, documentation
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: 4321.0.patch, HADOOP-4321.patch
>
>
> Document the capacity scheduler and related issues, some of which have touched the framework as well. The issues are all linked in HADOOP-3444.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4321) Document the capacity scheduler in
Forrest
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated HADOOP-4321:
----------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Hemanth!
> Document the capacity scheduler in Forrest
> ------------------------------------------
>
> Key: HADOOP-4321
> URL: https://issues.apache.org/jira/browse/HADOOP-4321
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched, documentation
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: 4321.0.patch, HADOOP-4321.patch, HADOOP-4321.patch
>
>
> Document the capacity scheduler and related issues, some of which have touched the framework as well. The issues are all linked in HADOOP-3444.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4321) Document the capacity scheduler in
Forrest
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala updated HADOOP-4321:
-------------------------------------
Attachment: HADOOP-4321.patch
Incorporated review comments.
Results of test patch continue to hold:
[exec] -1 overall.
[exec] +1 @author. The patch does not contain any @author tags.
[exec] -1 tests included. The patch doesn't appear to include any new or modified tests.
[exec] Please justify why no tests are needed for this patch.
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec] +1 findbugs. The patch does not introduce any new Findbugs warnings.
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
> Document the capacity scheduler in Forrest
> ------------------------------------------
>
> Key: HADOOP-4321
> URL: https://issues.apache.org/jira/browse/HADOOP-4321
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched, documentation
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: 4321.0.patch, HADOOP-4321.patch, HADOOP-4321.patch
>
>
> Document the capacity scheduler and related issues, some of which have touched the framework as well. The issues are all linked in HADOOP-3444.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4321) Document the capacity scheduler in
Forrest
Posted by "Vivek Ratan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vivek Ratan updated HADOOP-4321:
--------------------------------
Attachment: 4321.0.patch
Attaching patch that creates a Forrest document for the Capacity Scheduler.
> Document the capacity scheduler in Forrest
> ------------------------------------------
>
> Key: HADOOP-4321
> URL: https://issues.apache.org/jira/browse/HADOOP-4321
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched, documentation
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: 4321.0.patch
>
>
> Document the capacity scheduler and related issues, some of which have touched the framework as well. The issues are all linked in HADOOP-3444.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.