that's because sc is already initialized. You can do sc.stop() before you
initialize another one.

Thanks
Best Regards

On Fri, Jul 10, 2015 at 3:54 PM, Prateek . <prat...@aricent.com> wrote:

>  Hi,
>
>
>
> I am running single spark-shell but observing this error when I give val
> sc = new SparkContext(conf)
>
>
>
> 15/07/10 15:42:56 WARN AbstractLifeCycle: FAILED
> SelectChannelConnector@0.0.0.0:4040: java.net.BindException: Address
> already in use
>
> java.net.BindException: Address already in use
>
>         at sun.nio.ch.Net.bind0(Native Method)
>
>         at sun.nio.ch.Net.bind(Net.java:444)
>
>         at sun.nio.ch.Net.bind(Net.java:436)
>
>         at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
>
>         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>
>         at
> org.eclipse.jetty.server.nio.SelectChannelConnector.open(SelectChannelConnector.java:187)
>
>         at
> org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:316)
>
>         at
> org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:265)
>
>         at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>
>         at org.eclipse.jetty.server.Server.doStart(Server.java:293)
>
>         at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
>
>
>
>
>
> has any one come across the same issue , any suggestions?
>
>
>
> Thanks
>  "DISCLAIMER: This message is proprietary to Aricent and is intended
> solely for the use of the individual to whom it is addressed. It may
> contain privileged or confidential information and should not be circulated
> or used for any purpose other than for what it is intended. If you have
> received this message in error, please notify the originator immediately.
> If you are not the intended recipient, you are notified that you are
> strictly prohibited from using, copying, altering, or disclosing the
> contents of this message. Aricent accepts no responsibility for loss or
> damage arising from the use of the information transmitted by this email
> including damage from virus."
>

Reply via email to