[jira] [Resolved] (GIRAPH-23) Giraph causes capacity scheduler to report crazy statistics

["Jakob Homan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GIRAPH-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakob Homan resolved GIRAPH-23.
-------------------------------

    Resolution: Not A Problem

We tracked this down to the mapred.job.map.memory.mb and mapred.job.reducer.memory.mb settings which have to be set for 1.0 but not for 0.20.  Setting them causes the 0.20 JobTracker to go a bit crazy while the job is running, but this is a Hadoop problem, not a Giraph one.
                
> Giraph causes capacity scheduler to report crazy statistics
> -----------------------------------------------------------
>
>                 Key: GIRAPH-23
>                 URL: https://issues.apache.org/jira/browse/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.
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