Have you tried to connect to a drillbit directly from Zeppelin using the jdbc 
url jdbc:drill:drillbit=<hostname>:31010?

What does your drill-override.conf file look like?


> On Jul 11, 2016, at 2:33 PM, Krishnaprasad A S <krishna.pra...@flytxt.com> 
> wrote:
> 
> I can see all the 4 drillbits in ui. Aso I tried the query in web ui before
> running it in zeppelin. In web ui it works currently. Then what may be the
> issue.?
> On Jul 12, 2016 3:00 AM, "Andries Engelbrecht" <aengelbre...@maprtech.com>
> wrote:
> 
> What happens if you try to connect to a drillbit directly?
> 
> This will help to see if it is a zk connection issue.
> 
> Also I assume the dill cluster is up and running, and if you go to the
> webUI it shows all drillbits in the cluster connected and running.
> 
> 
>> On Jul 11, 2016, at 2:27 PM, Krishnaprasad A S <krishna.pra...@flytxt.com>
> wrote:
>> 
>> I went through the same link before configuring the interpreter, also
> there
>> is no security configured.
>> On Jul 12, 2016 2:48 AM, "Andries Engelbrecht" <aengelbre...@maprtech.com>
>> wrote:
>> 
>>> Do you have security configured on the Drill cluster? If so make sure to
>>> add the user and password info for the Drill connection.
>>> 
>>> Some good info for configuring Zeppelin with Drill here
>>> 
>>> https://community.mapr.com/docs/DOC-1493 <
>>> https://community.mapr.com/docs/DOC-1493>
>>> 
>>> --Andries
>>> 
>>> 
>>>> On Jul 11, 2016, at 2:13 PM, Krishnaprasad A S <
>>> krishna.pra...@flytxt.com> wrote:
>>>> 
>>>> My drill runs in clustered mode, with 4 drillbits running in 4 nodes. I
>>>> started it using drillbit.sh start command.
>>>> On Jul 12, 2016 2:18 AM, "Andries Engelbrecht" <
>>> aengelbre...@maprtech.com>
>>>> wrote:
>>>> 
>>>>> Are you running Drill in embedded mode or clustered mode?
>>>>> 
>>>>> If in embedded mode you may want to try to connect directly to the
>>> drillbit
>>>>> jdbc:drill:drillbit=<hostname>:31010
>>>>> 
>>>>> It looks like you are trying to connect to a zk with a drill cluster,
>>> and
>>>>> your setup may just be embedded mode.
>>>>> 
>>>>> --Andries
>>>>> 
>>>>> 
>>>>>> On Jul 11, 2016, at 12:55 PM, Krishnaprasad A S <
>>>>> krishna.pra...@flytxt.com> wrote:
>>>>>> 
>>>>>> hi,
>>>>>> I'm trying to create a drill interpreter in zeppelin using the
> existing
>>>>>> jdbc interpreter.
>>>>>> 
>>>>>> *drill.url = jdbc:drill:zk=<host>:2181/drill/drillbits1drill.driver =
>>>>>> org.apache.drill.jdbc.Driver*
>>>>>> my drillbit runs on the same server as of zeppelin.
>>>>>> 
>>>>>> Added the dependency
> 'apache-drill-1.7.0/jars/drill-jdbc-all-1.7.0.jar'
>>>>> in
>>>>>> zeppelin
>>>>>> I'm the getting the following error while running a sample SQL from
>>>>>> zeppelin,
>>>>>> 
>>>>>> ERROR [2016-07-12 01:11:41,946] ({pool-1-thread-4}
>>>>>> NotebookServer.java[afterStatusChange]:1135) - Error
>>>>>> org.apache.zeppelin.interpreter.InterpreterException:
>>>>>> org.apache.zeppelin.interpreter.InterpreterException:
>>>>>> org.apache.thrift.transport.TTransportException:
>>>>> java.net.ConnectException:
>>>>>> Connection refused
>>>>>>     at
>>>>>> 
>>>>> 
>>> 
> org.apache.zeppelin.interpreter.remote.RemoteInterpreter.init(RemoteInterpreter.java:165)
>>>>>>     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$Sync.innerRun(FutureTask.java:334)
>>>>>>     at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>>>>>>     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:1110)
>>>>>>     at
>>>>>> 
>>>>> 
>>> 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>>>>>>     at java.lang.Thread.run(Thread.java:722)
>>>>>> Caused by: org.apache.zeppelin.interpreter.InterpreterException:
>>>>>> org.apache.thrift.transport.TTransportException:
>>>>> java.net.ConnectException:
>>>>>> Connection refused
>>>>>>     at
>>>>>> 
>>>>> 
>>> 
> org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:53)
>>>>>>     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)
>>>>>>     ... 13 more
>>>>>> Caused by: org.apache.thrift.transport.TTransportException:
>>>>>> java.net.ConnectException: Connection refused
>>>>>>     at org.apache.thrift.transport.TSocket.open(TSocket.java:187)
>>>>>>     at
>>>>>> 
>>>>> 
>>> 
> org.apache.zeppelin.interpreter.remote.ClientFactory.create(ClientFactory.java:51)
>>>>>>     ... 20 more
>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>> 
>>>>> 
>>> 
>>> 

Reply via email to