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

Thomas Graves commented on MAPREDUCE-3680:
------------------------------------------

Hey B Anil Kumar, 

Thanks for the patch.  It looks good other then the test failures. Can you 
update TestRMWebServices (function verifyClusterSchedulerFifoGeneric) to expect 
0 instead of the NaN now?  

A very minor nit if you want to fix is Scheduler is misspelled in the test 
function title: testFifoSchedularCapacityWhenNoNMs



As a side note this also fixes the mapred queue -info output:

with patch:
$ mapred queue -info default
======================
Queue Name : default 
Queue State : running 
Scheduling Info : Capacity: 100.0, MaximumCapacity: 1.0, CurrentCapacity: 0.0 


without:
$ mapred queue -info default
======================
Queue Name : default 
Queue State : running 
Scheduling Info : Capacity: 100.0, MaximumCapacity: 1.0, CurrentCapacity: NaN 

                
> FifoScheduler web service rest API can print out invalid JSON
> -------------------------------------------------------------
>
>                 Key: MAPREDUCE-3680
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3680
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Thomas Graves
>         Attachments: MAPREDUCE-3680.patch
>
>
> running a GET on the scheduler web services rest api 
> (RM:port/ws/cluster/scheduler) with the FifoScheduler configured with no 
> nodemanagers up yet and it prints out invalid json of NaN for the used 
> Capacity:
> {"scheduler":{"schedulerInfo":{"type":"fifoScheduler","capacity":1.0,"usedCapacity":NaN,"qstate":"RUNNING","minQueueMemoryCapacity":1024,"maxQueueMemoryCapacity":10240,"numNodes":0,"usedNodeCapacity":0,"availNodeCapacity":0,"totalNodeCapacity":0,"numContainers":0}}}

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

        

Reply via email to