giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jake Mannix (Created) (JIRA)" <>
Subject [jira] [Created] (GIRAPH-72) Running multiple Giraph jobs on the same cluster can lead to port collisions
Date Thu, 03 Nov 2011 01:17:32 GMT
Running multiple Giraph jobs on the same cluster can lead to port collisions

                 Key: GIRAPH-72
             Project: Giraph
          Issue Type: Bug
          Components: lib, zookeeper
    Affects Versions: 0.70.0
         Environment: production hadoop cluster, in-process ZK.
            Reporter: Jake Mannix

Had a Giraph mini-hackathon at work today, and lots of us launched simultaneous test jobs
at the same time, and often ran into the following collision:

startSuperstep: WORKER_ONLY - Attempt=0, Superstep=-1
2-Nov-2011 23:40:08 Problem binding to <hostname>/<hostIP>:30000 : Address
already in use
	at org.apache.hadoop.ipc.Server.bind(
	at org.apache.hadoop.ipc.Server$Listener.(
	at org.apache.hadoop.ipc.Server.(
	at org.apache.hadoop.ipc.RPC$Server.(
	at org.apache.hadoop.ipc.RPC.getServer(
	at org.apache.giraph.comm.RPCCommunications.getRPCServer(
	at org.apache.giraph.comm.BasicRPCCommunications.(
	at org.apache.giraph.comm.RPCCommunications.(
	at org.apache.hadoop.mapred.MapTask.runNewMapper(
	at org.apache.hadoop.mapred.Child.main(
Caused by: Address already in use
	at Method)
	at org.apache.hadoop.ipc.Server.bind(
	... 12 more

The job then simply hung.  What it should do, I'd imagine, is at a bare minimum, catch this
exception and allow the task to die quickly so it can get retried on another machine, or better
yet, allow for a command-line arg at startup (and then passed into the Configuration) decide
what ports to use.  Best yet, something automagic which allows multiple GraphMappers on the
same machine without manually picking ports (pick one at random and store it in zookeeper?
 but then what about the in-process zookeeper...) 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message