[
https://issues.apache.org/jira/browse/HADOOP-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656618#action_12656618
]
Hadoop QA commented on HADOOP-4774:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12396068/HADOOP-4774-3.patch
against trunk revision 726129.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 5 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3745/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3745/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3745/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3745/console
This message is automatically generated.
> CapacityScheduler should work even if capacity-scheduler.xml is not in the
> classpath i.e with the code defaults
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4774
> URL: https://issues.apache.org/jira/browse/HADOOP-4774
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Amar Kamat
> Assignee: Sreekanth Ramakrishnan
> Attachments: HADOOP-4774-1.patch, HADOOP-4774-2.patch,
> HADOOP-4774-3.patch
>
>
> If I try running capacity-scheduler without having capacity-scheduler.xml in
> my class path, the jobtracker fails with the following error
> {code}
> Invalid initializater poller interval -1
> {code}
> I feel the problem lies with the default value assigned to it in the code.
> The capacity-scheduler conf says the default is 5000.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
