Giraph causes capacity scheduler to report crazy statistics

                 Key: GIRAPH-23
             Project: Giraph
          Issue Type: Bug
         Environment: Hadoop 20.2, non-secure with capacity scheduler
            Reporter: Jakob Homan

Not sure why, but all our Giraph jobs create crazy values for the scheduler in 
terms of number of mappers:
{noformat}51 running map tasks using -52224 map slots, 0 running reduce tasks 
using 0 reduce slots. {noformat}
and this trickles out to the whole cluster:
{noformat}Used capacity: -58229 (-12468.7% of Capacity){noformat}
These numbers don't appear to affect the job and the correct themselves a short 
time after the Giraph job finishes running.

This message is automatically generated by JIRA.
For more information on JIRA, see:


Reply via email to