Whoopdeedoo, after just waiting for like an hour (well, I was doing other stuff) the process holding that address seems to have died automatically and now I can start up pyspark without any warnings.
Would there be a faster way to go through this than just wait around for the orphaned process to die? Nick On Wed, Mar 5, 2014 at 1:01 PM, Nicholas Chammas <nicholas.cham...@gmail.com > wrote: > So I was doing stuff in pyspark on a cluster in EC2. I got booted due to a > network issue. I reconnect to the cluster and start up pyspark again. I get > these warnings: > > 14/03/05 17:54:56 WARN component.AbstractLifeCycle: FAILED > SelectChannelConnector@0.0.0.0:4040: java.net.BindException: Address > already in use > > Is this Bad(tm)? Do I need to do anything? sc appears to be available as > usual. > > Nick > > > ------------------------------ > View this message in context: disconnected from cluster; reconnecting > gives > java.net.BindException<http://apache-spark-user-list.1001560.n3.nabble.com/disconnected-from-cluster-reconnecting-gives-java-net-BindException-tp2309.html> > Sent from the Apache Spark User List mailing list > archive<http://apache-spark-user-list.1001560.n3.nabble.com/>at Nabble.com. >
