[jira] [Created] (GIRAPH-1001) GiraphJob#checkLocalJobRunnerConfiguration fails on Hadoop2 when MRv1 classes are on the classpath

["Gabriel Reid (JIRA)" <ji...@apache.org>]

Gabriel Reid created GIRAPH-1001:
------------------------------------

             Summary: GiraphJob#checkLocalJobRunnerConfiguration fails on Hadoop2 when MRv1 classes are on the classpath
                 Key: GIRAPH-1001
                 URL: https://issues.apache.org/jira/browse/GIRAPH-1001
             Project: Giraph
          Issue Type: Bug
            Reporter: Gabriel Reid


The checks in o.a.g.job.GiraphJob#checkLocalJobRunnerConfiguration make use of the deprecated "mapred.job.tracker" property to check if the local job tracker is being used. 

This seems to be an issue in some configurations where MRv1 jars (with mapred-default.xml) are present on the classpath, as the local job tracker is not being used, but the mapred.job.tracker property default is also no overwritten (because it is deprecated). This makes it impossible to run Giraph in such a situation without adding a "fake" mapred.job.tracker entry to the mapred-site.xml config.

Ideally, this check should make use of the mapreduce.framework.name and mapreduce.jobtracker.address properties before falling back to the mapred.job.tracker property to check if the local job tracker is being used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)