Hi, I am also facing the similar issue.
I am using zeppelin 0.6.0 pre-built binary version with spark 1.6.2 on my windows laptop and everything is working fine. After upgrading to spark 2.0, zeppelin is giving me below error in UI. Also, Please find the attached log file for more details. Code: ===== %spark var test = "Hello" Zeppelin UI Error: ============= java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.connect0(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at org.apache.thrift.transport.TSocket.open(TSocket.java:182) at org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:51) at org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:37) at org.apache.commons.pool2.BasePooledObjectFactory.makeObject(BasePooledObjectFactory.java:60) at org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:861) at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435) at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363) at org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess.getClient(RemoteInterpreterProcess.java:184) at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.init(RemoteInterpreter.java:163) at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getFormType(RemoteInterpreter.java:328) at org.apache.zeppelin.interpreter.LazyOpenInterpreter.getFormType(LazyOpenInterpreter.java:105) at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:260) at org.apache.zeppelin.scheduler.Job.run(Job.java:176) at org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:328) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) On Sat, Oct 15, 2016 at 8:11 AM, Xi Shen <[email protected]> wrote: > Hi, > > By "local Spark 2.0 instance", did you mean a standalone cluster on your > local? So you updated the "master", and "deploy-mode" interpreter > configuration? > > I had this problem as well. But I found if you set the > "spark.executor.memory" to "512m", and make sure your machine has > sufficient physical memory, it is less likely to hit this problem. > > If this is not your case, please share your ./logs/zeppelin*spark*.log, so > people can help you take a look. > > > On Fri, Oct 14, 2016 at 11:24 PM soralee <[email protected]> wrote: > >> Hi >> Thanks for your kind answers :) >> >> I downloaded file through your url link and I've tested. >> This test have executed a "bin/zeppelin.cmd" command in cmd window. >> But, I didn't find your problem. >> >> Did you get the other error logs? >> This "logs" folder is under zeppelin's home. >> >> If not, when you execute your spark paragraph(such as "var a=1"), please >> let >> me know the whole error logs. >> >> >> Thanks, >> Sora >> >> >> >> -- >> View this message in context: http://apache-zeppelin-users- >> incubating-mailing-list.75479.x6.nabble.com/Zeppelin-0-6-1- >> not-connecting-to-Spark-2-0-on-Windows-tp4270p4359.html >> Sent from the Apache Zeppelin Users (incubating) mailing list mailing >> list archive at Nabble.com. >> > -- > > > Thanks, > David S. > -- Thanks & Regards *Vivek Narayanasetty* *Go Green: Think before you print this e-mail or its attachment. You can save paper if you do not really need to print.*
zeppelin-username-D330N6C2.log
Description: Binary data
