Hey Avery, Thanks a bunch for responding so quickly to my post! Looks like the problem is with my client class. When I attempt to run one of the Giraph examples, which use GiraphRunner, GiraphRunner connects to the correct port and launches the Giraph job. So....I just need to take a closer look at GiraphRunner.
Thanks again for your quick response--much appreciated. --John On Sun, Jun 1, 2014 at 11:12 AM, Avery Ching <ach...@apache.org> wrote: > Giraph should just pick up your cluster's HDFS configuration. Can you > check your hadoop *.xml files? > > > On 6/1/14, 3:34 AM, John Yost wrote: > > Hi Everyone, > > Not sure why, but Giraph tries to connect to port 9000: > > java.net.ConnectException: Call From localhost.localdomain/127.0.0.1 to > localhost:9000 failed on connection exception: java.net.ConnectException: > Connection refused; For more details see: > http://wiki.apache.org/hadoop/ConnectionRefused > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > > I set the following in the Giraph configuration: > > GiraphConstants.IS_PURE_YARN_JOB.set(conf,true); > conf.set("giraph.useNetty","true"); > conf.set("giraph.zkList","localhost.localdomain"); > > conf.set("fs.defaultFS","hdfs://localhost.localdomain:8020") > conf.set("mapreduce.job.tracker","localhost.localdomain:54311"); > conf.set("mapreduce.framework.name","yarn"); > > conf.set("yarn.resourcemanager.address","localhost.localdomain:8032"); > > I built Giraph as follows: > > mvn -DskipTests=true -Dhadoop.version=2.2.0 -Phadoop_yarn clean install > > Any ideas as to why Giraph attempts to connect to 9000 instead of 8020? > > --John > > > >
