You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@drill.apache.org by lapro1 <la...@gmail.com> on 2014/11/18 16:23:26 UTC

Drill web interface, and zookeeper connection

Hi,
I would have two questions about drill.
First is, what could be the problem with my drillbit, or is it a standard
effect with it? When I start drillbit, the command line comes back shortly,
and it looks like, it is started. On the other hand, when I'd like to
 connect to it from web interface, I can't, approximately for 1-2 minutes.

Second question is: according to the starting drill section of the link
below

https://cwiki.apache.org/confluence/display/DRILL/Deploying+Apache+Drill+in+a+Clustered+Environment

it writes, that I don't have to give directly the zookeeper's host and port
to sql line interface. I see it writes, if the interface doesn't work
without those parameters, then give it, but is it have any reason?
(Obviously, it doesn't work for me too without them.)
Thanks in advance the anwser.
Laszlo

Re: Drill web interface, and zookeeper connection

Posted by lapro1 <la...@gmail.com>.
Hi,

I created a JIRA post for it. I copied 3 log file's last  lines. They were
huge, but I hope this will be enough. (sqlline.log, rillbit.log,
drillbit.out)

The post is: https://issues.apache.org/jira/browse/DRILL-1758

Thanks,
Laszlo

Re: Drill web interface, and zookeeper connection

Posted by lapro1 <la...@gmail.com>.
Hi,

I created a JIRA post for it. I copied 3 log file's last  lines. They were
huge, but I hope this will be enough. (sqlline.log, rillbit.log,
drillbit.out)

The post is: https://issues.apache.org/jira/browse/DRILL-1758

Thanks,
Laszlo

Re: Drill web interface, and zookeeper connection

Posted by Hanifi Gunes <hg...@maprtech.com>.
Hi Laszlo,

Can you open up a JIRA and upload your entire log so that devs can take a
look at the problem?

https://issues.apache.org/jira/browse/DRILL

Thanks.
-Hanifi

Re: Drill web interface, and zookeeper connection

Posted by Hanifi Gunes <hg...@maprtech.com>.
Hi Laszlo,

Can you open up a JIRA and upload your entire log so that devs can take a
look at the problem?

https://issues.apache.org/jira/browse/DRILL

Thanks.
-Hanifi

Re: Drill web interface, and zookeeper connection

Posted by lapro1 <la...@gmail.com>.
Hi,
I insert here the last 100 line of drillbit.out. I queried it frequently,
while my drillbit was starting. It was interesting, because the last 7-8
lines of the log below was appeared, only when I could access to it with
web interface.
I think it can couse the problem what I have written in another thread too,
with subject:* Drill stops immediately*
Please help me in it, if you see anyting useful from the log.



[root@sandbox ~]# /opt/drill/bin/drillbit.sh start
Drill log directory /var/log/drill does not exist, defaulting to
/opt/drill/log
starting drillbit, logging to /opt/drill/log/drillbit.out
[root@sandbox ~]# tail -n 30  /opt/drill/log/drillbit.out
   Locked ownable synchronizers:
        - None

"Reference Handler" daemon prio=10 tid=0x00007f7d480eb000 nid=0x11f1 in
Object.wait() [0x00007f7cff009000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:503)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
        - locked <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)

   Locked ownable synchronizers:
        - None

"VM Thread" prio=10 tid=0x00007f7d480e8800 nid=0x11f0 runnable

"Gang worker#0 (Parallel GC Threads)" prio=10 tid=0x00007f7d4801f000
nid=0x11eb runnable

"Gang worker#1 (Parallel GC Threads)" prio=10 tid=0x00007f7d48021000
nid=0x11ec runnable

"Gang worker#2 (Parallel GC Threads)" prio=10 tid=0x00007f7d48023000
nid=0x11ed runnable

"Gang worker#3 (Parallel GC Threads)" prio=10 tid=0x00007f7d48024800
nid=0x11ee runnable

"Concurrent Mark-Sweep GC Thread" prio=10 tid=0x00007f7d480a5000 nid=0x11ef
runnable
"VM Periodic Task Thread" prio=10 tid=0x00007f7d48122800 nid=0x11f8 waiting
on condition

JNI global references: 356

/opt/drill/bin/drillbit.sh: line 189:  4557 Killed                  nice -n
$DRILL_NICENESS "$DRILL_HOME"/bin/runbit $command "$@" start >> "$logout"
2>&1
[root@sandbox ~]# tail -n 30  /opt/drill/log/drillbit.out
        - waiting on <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:503)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
        - locked <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)

   Locked ownable synchronizers:
        - None

"VM Thread" prio=10 tid=0x00007f7d480e8800 nid=0x11f0 runnable

"Gang worker#0 (Parallel GC Threads)" prio=10 tid=0x00007f7d4801f000
nid=0x11eb runnable

"Gang worker#1 (Parallel GC Threads)" prio=10 tid=0x00007f7d48021000
nid=0x11ec runnable

"Gang worker#2 (Parallel GC Threads)" prio=10 tid=0x00007f7d48023000
nid=0x11ed runnable

"Gang worker#3 (Parallel GC Threads)" prio=10 tid=0x00007f7d48024800
nid=0x11ee runnable

"Concurrent Mark-Sweep GC Thread" prio=10 tid=0x00007f7d480a5000 nid=0x11ef
runnable
"VM Periodic Task Thread" prio=10 tid=0x00007f7d48122800 nid=0x11f8 waiting
on condition

JNI global references: 356

/opt/drill/bin/drillbit.sh: line 189:  4557 Killed                  nice -n
$DRILL_NICENESS "$DRILL_HOME"/bin/runbit $command "$@" start >> "$logout"
2>&1
log4j:WARN No appenders could be found for logger (org.jboss.logging).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
Nov 19, 2014 9:23:44 AM org.glassfish.jersey.server.ApplicationHandler
initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
01:25:26...

[root@sandbox ~]# tail -n 100  /opt/drill/log/drillbit.out
        - waiting on <0x00000006f4d03d58> (a java.lang.Object)
        at
de.huxhorn.lilith.sender.SimpleSendBytesService$SendBytesThread$ReconnectionThread.run(SimpleSendBytesService.java:350)
        - locked <0x00000006f4d03d58> (a java.lang.Object)

   Locked ownable synchronizers:
        - None

"SendBytes@SocketDataOutputStreamFactory[hostName=localhost, port=10000,
connectionTimeout=10000, writeTimeout=5000]" daemon prio=10
tid=0x00007f7d48883000 nid=0x11fb runnable [0x00007f7cfdddf000]
   java.lang.Thread.State: RUNNABLE
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
        at
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.write(BufferedOutputStream.java:126)
        - locked <0x00000006f51277b0> (a java.io.BufferedOutputStream)
        at
de.huxhorn.sulky.io.TimeoutOutputStream.write(TimeoutOutputStream.java:109)
        at java.io.DataOutputStream.write(DataOutputStream.java:107)
        - locked <0x00000006f5127368> (a java.io.DataOutputStream)
        at java.io.FilterOutputStream.write(FilterOutputStream.java:97)
        at
de.huxhorn.lilith.sender.MessageWriteByteStrategy.writeBytes(MessageWriteByteStrategy.java:56)
        at
de.huxhorn.lilith.sender.SimpleSendBytesService$SendBytesThread.run(SimpleSendBytesService.java:243)

   Locked ownable synchronizers:
        - None

"Service Thread" daemon prio=10 tid=0x00007f7d48117000 nid=0x11f7 runnable
[0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"C2 CompilerThread1" daemon prio=10 tid=0x00007f7d48114800 nid=0x11f6
waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"C2 CompilerThread0" daemon prio=10 tid=0x00007f7d48112800 nid=0x11f5
waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"Signal Dispatcher" daemon prio=10 tid=0x00007f7d48110000 nid=0x11f4
runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"Surrogate Locker Thread (Concurrent GC)" daemon prio=10
tid=0x00007f7d48106000 nid=0x11f3 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"Finalizer" daemon prio=10 tid=0x00007f7d480ef000 nid=0x11f2 in
Object.wait() [0x00007f7cfef08000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000006f4ce5ca0> (a
java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
        - locked <0x00000006f4ce5ca0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
        at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:189)

   Locked ownable synchronizers:
        - None

"Reference Handler" daemon prio=10 tid=0x00007f7d480eb000 nid=0x11f1 in
Object.wait() [0x00007f7cff009000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:503)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
        - locked <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)

   Locked ownable synchronizers:
        - None

"VM Thread" prio=10 tid=0x00007f7d480e8800 nid=0x11f0 runnable

"Gang worker#0 (Parallel GC Threads)" prio=10 tid=0x00007f7d4801f000
nid=0x11eb runnable

"Gang worker#1 (Parallel GC Threads)" prio=10 tid=0x00007f7d48021000
nid=0x11ec runnable

"Gang worker#2 (Parallel GC Threads)" prio=10 tid=0x00007f7d48023000
nid=0x11ed runnable

"Gang worker#3 (Parallel GC Threads)" prio=10 tid=0x00007f7d48024800
nid=0x11ee runnable

"Concurrent Mark-Sweep GC Thread" prio=10 tid=0x00007f7d480a5000 nid=0x11ef
runnable
"VM Periodic Task Thread" prio=10 tid=0x00007f7d48122800 nid=0x11f8 waiting
on condition

JNI global references: 356

/opt/drill/bin/drillbit.sh: line 189:  4557 Killed                  nice -n
$DRILL_NICENESS "$DRILL_HOME"/bin/runbit $command "$@" start >> "$logout"
2>&1
log4j:WARN No appenders could be found for logger (org.jboss.logging).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
Nov 19, 2014 9:23:44 AM org.glassfish.jersey.server.ApplicationHandler
initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
01:25:26...





Thanks in advance, Laszlo




2014-11-19 6:14 GMT+01:00 mufy <mu...@gmail.com>:

> Hello Laszlo,
>
> What version of Drill are you using? Did you get a chance to see the events
> registered in the drillbit.log?
>
>
> ---
> Mufeed Usman
> My LinkedIn <http://www.linkedin.com/pub/mufeed-usman/28/254/400> | My
> Social Cause <http://www.vision2016.org.in/> | My Blogs : LiveJournal
> <http://mufeed.livejournal.com>
>
>
>
>
> On Tue, Nov 18, 2014 at 8:53 PM, lapro1 <la...@gmail.com> wrote:
>
> > Hi,
> > I would have two questions about drill.
> > First is, what could be the problem with my drillbit, or is it a standard
> > effect with it? When I start drillbit, the command line comes back
> shortly,
> > and it looks like, it is started. On the other hand, when I'd like to
> >  connect to it from web interface, I can't, approximately for 1-2
> minutes.
> >
> > Second question is: according to the starting drill section of the link
> > below
> >
> >
> >
> https://cwiki.apache.org/confluence/display/DRILL/Deploying+Apache+Drill+in+a+Clustered+Environment
> >
> > it writes, that I don't have to give directly the zookeeper's host and
> port
> > to sql line interface. I see it writes, if the interface doesn't work
> > without those parameters, then give it, but is it have any reason?
> > (Obviously, it doesn't work for me too without them.)
> > Thanks in advance the anwser.
> > Laszlo
> >
>

Re: Drill web interface, and zookeeper connection

Posted by lapro1 <la...@gmail.com>.
Hi,
I insert here the last 100 line of drillbit.out. I queried it frequently,
while my drillbit was starting. It was interesting, because the last 7-8
lines of the log below was appeared, only when I could access to it with
web interface.
I think it can couse the problem what I have written in another thread too,
with subject:* Drill stops immediately*
Please help me in it, if you see anyting useful from the log.



[root@sandbox ~]# /opt/drill/bin/drillbit.sh start
Drill log directory /var/log/drill does not exist, defaulting to
/opt/drill/log
starting drillbit, logging to /opt/drill/log/drillbit.out
[root@sandbox ~]# tail -n 30  /opt/drill/log/drillbit.out
   Locked ownable synchronizers:
        - None

"Reference Handler" daemon prio=10 tid=0x00007f7d480eb000 nid=0x11f1 in
Object.wait() [0x00007f7cff009000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:503)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
        - locked <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)

   Locked ownable synchronizers:
        - None

"VM Thread" prio=10 tid=0x00007f7d480e8800 nid=0x11f0 runnable

"Gang worker#0 (Parallel GC Threads)" prio=10 tid=0x00007f7d4801f000
nid=0x11eb runnable

"Gang worker#1 (Parallel GC Threads)" prio=10 tid=0x00007f7d48021000
nid=0x11ec runnable

"Gang worker#2 (Parallel GC Threads)" prio=10 tid=0x00007f7d48023000
nid=0x11ed runnable

"Gang worker#3 (Parallel GC Threads)" prio=10 tid=0x00007f7d48024800
nid=0x11ee runnable

"Concurrent Mark-Sweep GC Thread" prio=10 tid=0x00007f7d480a5000 nid=0x11ef
runnable
"VM Periodic Task Thread" prio=10 tid=0x00007f7d48122800 nid=0x11f8 waiting
on condition

JNI global references: 356

/opt/drill/bin/drillbit.sh: line 189:  4557 Killed                  nice -n
$DRILL_NICENESS "$DRILL_HOME"/bin/runbit $command "$@" start >> "$logout"
2>&1
[root@sandbox ~]# tail -n 30  /opt/drill/log/drillbit.out
        - waiting on <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:503)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
        - locked <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)

   Locked ownable synchronizers:
        - None

"VM Thread" prio=10 tid=0x00007f7d480e8800 nid=0x11f0 runnable

"Gang worker#0 (Parallel GC Threads)" prio=10 tid=0x00007f7d4801f000
nid=0x11eb runnable

"Gang worker#1 (Parallel GC Threads)" prio=10 tid=0x00007f7d48021000
nid=0x11ec runnable

"Gang worker#2 (Parallel GC Threads)" prio=10 tid=0x00007f7d48023000
nid=0x11ed runnable

"Gang worker#3 (Parallel GC Threads)" prio=10 tid=0x00007f7d48024800
nid=0x11ee runnable

"Concurrent Mark-Sweep GC Thread" prio=10 tid=0x00007f7d480a5000 nid=0x11ef
runnable
"VM Periodic Task Thread" prio=10 tid=0x00007f7d48122800 nid=0x11f8 waiting
on condition

JNI global references: 356

/opt/drill/bin/drillbit.sh: line 189:  4557 Killed                  nice -n
$DRILL_NICENESS "$DRILL_HOME"/bin/runbit $command "$@" start >> "$logout"
2>&1
log4j:WARN No appenders could be found for logger (org.jboss.logging).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
Nov 19, 2014 9:23:44 AM org.glassfish.jersey.server.ApplicationHandler
initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
01:25:26...

[root@sandbox ~]# tail -n 100  /opt/drill/log/drillbit.out
        - waiting on <0x00000006f4d03d58> (a java.lang.Object)
        at
de.huxhorn.lilith.sender.SimpleSendBytesService$SendBytesThread$ReconnectionThread.run(SimpleSendBytesService.java:350)
        - locked <0x00000006f4d03d58> (a java.lang.Object)

   Locked ownable synchronizers:
        - None

"SendBytes@SocketDataOutputStreamFactory[hostName=localhost, port=10000,
connectionTimeout=10000, writeTimeout=5000]" daemon prio=10
tid=0x00007f7d48883000 nid=0x11fb runnable [0x00007f7cfdddf000]
   java.lang.Thread.State: RUNNABLE
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
        at
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.write(BufferedOutputStream.java:126)
        - locked <0x00000006f51277b0> (a java.io.BufferedOutputStream)
        at
de.huxhorn.sulky.io.TimeoutOutputStream.write(TimeoutOutputStream.java:109)
        at java.io.DataOutputStream.write(DataOutputStream.java:107)
        - locked <0x00000006f5127368> (a java.io.DataOutputStream)
        at java.io.FilterOutputStream.write(FilterOutputStream.java:97)
        at
de.huxhorn.lilith.sender.MessageWriteByteStrategy.writeBytes(MessageWriteByteStrategy.java:56)
        at
de.huxhorn.lilith.sender.SimpleSendBytesService$SendBytesThread.run(SimpleSendBytesService.java:243)

   Locked ownable synchronizers:
        - None

"Service Thread" daemon prio=10 tid=0x00007f7d48117000 nid=0x11f7 runnable
[0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"C2 CompilerThread1" daemon prio=10 tid=0x00007f7d48114800 nid=0x11f6
waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"C2 CompilerThread0" daemon prio=10 tid=0x00007f7d48112800 nid=0x11f5
waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"Signal Dispatcher" daemon prio=10 tid=0x00007f7d48110000 nid=0x11f4
runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"Surrogate Locker Thread (Concurrent GC)" daemon prio=10
tid=0x00007f7d48106000 nid=0x11f3 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
        - None

"Finalizer" daemon prio=10 tid=0x00007f7d480ef000 nid=0x11f2 in
Object.wait() [0x00007f7cfef08000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000006f4ce5ca0> (a
java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
        - locked <0x00000006f4ce5ca0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
        at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:189)

   Locked ownable synchronizers:
        - None

"Reference Handler" daemon prio=10 tid=0x00007f7d480eb000 nid=0x11f1 in
Object.wait() [0x00007f7cff009000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:503)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
        - locked <0x00000006f4ce5cb8> (a java.lang.ref.Reference$Lock)

   Locked ownable synchronizers:
        - None

"VM Thread" prio=10 tid=0x00007f7d480e8800 nid=0x11f0 runnable

"Gang worker#0 (Parallel GC Threads)" prio=10 tid=0x00007f7d4801f000
nid=0x11eb runnable

"Gang worker#1 (Parallel GC Threads)" prio=10 tid=0x00007f7d48021000
nid=0x11ec runnable

"Gang worker#2 (Parallel GC Threads)" prio=10 tid=0x00007f7d48023000
nid=0x11ed runnable

"Gang worker#3 (Parallel GC Threads)" prio=10 tid=0x00007f7d48024800
nid=0x11ee runnable

"Concurrent Mark-Sweep GC Thread" prio=10 tid=0x00007f7d480a5000 nid=0x11ef
runnable
"VM Periodic Task Thread" prio=10 tid=0x00007f7d48122800 nid=0x11f8 waiting
on condition

JNI global references: 356

/opt/drill/bin/drillbit.sh: line 189:  4557 Killed                  nice -n
$DRILL_NICENESS "$DRILL_HOME"/bin/runbit $command "$@" start >> "$logout"
2>&1
log4j:WARN No appenders could be found for logger (org.jboss.logging).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
Nov 19, 2014 9:23:44 AM org.glassfish.jersey.server.ApplicationHandler
initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
01:25:26...





Thanks in advance, Laszlo




2014-11-19 6:14 GMT+01:00 mufy <mu...@gmail.com>:

> Hello Laszlo,
>
> What version of Drill are you using? Did you get a chance to see the events
> registered in the drillbit.log?
>
>
> ---
> Mufeed Usman
> My LinkedIn <http://www.linkedin.com/pub/mufeed-usman/28/254/400> | My
> Social Cause <http://www.vision2016.org.in/> | My Blogs : LiveJournal
> <http://mufeed.livejournal.com>
>
>
>
>
> On Tue, Nov 18, 2014 at 8:53 PM, lapro1 <la...@gmail.com> wrote:
>
> > Hi,
> > I would have two questions about drill.
> > First is, what could be the problem with my drillbit, or is it a standard
> > effect with it? When I start drillbit, the command line comes back
> shortly,
> > and it looks like, it is started. On the other hand, when I'd like to
> >  connect to it from web interface, I can't, approximately for 1-2
> minutes.
> >
> > Second question is: according to the starting drill section of the link
> > below
> >
> >
> >
> https://cwiki.apache.org/confluence/display/DRILL/Deploying+Apache+Drill+in+a+Clustered+Environment
> >
> > it writes, that I don't have to give directly the zookeeper's host and
> port
> > to sql line interface. I see it writes, if the interface doesn't work
> > without those parameters, then give it, but is it have any reason?
> > (Obviously, it doesn't work for me too without them.)
> > Thanks in advance the anwser.
> > Laszlo
> >
>

Re: Drill web interface, and zookeeper connection

Posted by mufy <mu...@gmail.com>.
Hello Laszlo,

What version of Drill are you using? Did you get a chance to see the events
registered in the drillbit.log?


---
Mufeed Usman
My LinkedIn <http://www.linkedin.com/pub/mufeed-usman/28/254/400> | My
Social Cause <http://www.vision2016.org.in/> | My Blogs : LiveJournal
<http://mufeed.livejournal.com>




On Tue, Nov 18, 2014 at 8:53 PM, lapro1 <la...@gmail.com> wrote:

> Hi,
> I would have two questions about drill.
> First is, what could be the problem with my drillbit, or is it a standard
> effect with it? When I start drillbit, the command line comes back shortly,
> and it looks like, it is started. On the other hand, when I'd like to
>  connect to it from web interface, I can't, approximately for 1-2 minutes.
>
> Second question is: according to the starting drill section of the link
> below
>
>
> https://cwiki.apache.org/confluence/display/DRILL/Deploying+Apache+Drill+in+a+Clustered+Environment
>
> it writes, that I don't have to give directly the zookeeper's host and port
> to sql line interface. I see it writes, if the interface doesn't work
> without those parameters, then give it, but is it have any reason?
> (Obviously, it doesn't work for me too without them.)
> Thanks in advance the anwser.
> Laszlo
>

Re: Drill web interface, and zookeeper connection

Posted by mufy <mu...@gmail.com>.
Hello Laszlo,

What version of Drill are you using? Did you get a chance to see the events
registered in the drillbit.log?


---
Mufeed Usman
My LinkedIn <http://www.linkedin.com/pub/mufeed-usman/28/254/400> | My
Social Cause <http://www.vision2016.org.in/> | My Blogs : LiveJournal
<http://mufeed.livejournal.com>




On Tue, Nov 18, 2014 at 8:53 PM, lapro1 <la...@gmail.com> wrote:

> Hi,
> I would have two questions about drill.
> First is, what could be the problem with my drillbit, or is it a standard
> effect with it? When I start drillbit, the command line comes back shortly,
> and it looks like, it is started. On the other hand, when I'd like to
>  connect to it from web interface, I can't, approximately for 1-2 minutes.
>
> Second question is: according to the starting drill section of the link
> below
>
>
> https://cwiki.apache.org/confluence/display/DRILL/Deploying+Apache+Drill+in+a+Clustered+Environment
>
> it writes, that I don't have to give directly the zookeeper's host and port
> to sql line interface. I see it writes, if the interface doesn't work
> without those parameters, then give it, but is it have any reason?
> (Obviously, it doesn't work for me too without them.)
> Thanks in advance the anwser.
> Laszlo
>