Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Drill >> mail # user >> Distributed mode troubles: ZK/Curator connection time out


Copy link to this message
-
Re: Distributed mode troubles: ZK/Curator connection time out
Actually, I am wrong, Drill does not start a zookeeper when running in
local mode. The LocalClusterCoordinator does not use zookeeper at all.
On Sun, Oct 27, 2013 at 3:44 PM, Steven Phillips <[EMAIL PROTECTED]>wrote:

> Drill will start a zookeeper only in embedded mode. For example, running
> sqlline using parquet-local will launch a drillbit and zk all within one
> JVM.
>
> But to run a standalone drillbit requires an external zookeeper.
>
>
> On Sun, Oct 27, 2013 at 3:39 PM, Michael Hausenblas <
> [EMAIL PROTECTED]> wrote:
>
>>
>> Maybe I'm dense but I thought Drill starts a ZK? Or do I have to install
>> and launch ZK separately?
>>
>> I'm using the binary version of M1. Run all things local only on my
>> laptop ...
>>
>> Cheers,
>>              Michael
>>
>> Sent from my iPad
>>
>> --
>> Michael Hausenblas, http://mhausenblas.info
>>
>> > On 27 Oct 2013, at 22:17, Steven Phillips <[EMAIL PROTECTED]>
>> wrote:
>> >
>> > You need to replace localhost with the hostname of the node running
>> > zookeeper. If that zookeeper is configured to use a port different than
>> > 2181, then that needs to be set as well. If you have multiple
>> zookeepers in
>> > the quorum, you then zk.connect should be a comma separated list of the
>> > host:port of each node.
>> >
>> > The default, localhost setting will only work when a drillbit is
>> running on
>> > the same node as the zookeeper.
>> >
>> >
>> > On Sun, Oct 27, 2013 at 2:57 PM, Michael Hausenblas <
>> > [EMAIL PROTECTED]> wrote:
>> >
>> >>
>> >>> One thing to add to the diagram is that all of the drill java
>> processes
>> >> will look at what is in drill-override.conf.
>> >>
>> >> Thanks, done.
>> >>
>> >>
>> >>> You must set zk.connect to the correct zk host:port.
>> >>
>> >>
>> >> Can you be a tad more explicit, please? In drill-override.conf I have
>> >>
>> >> [[
>> >> …
>> >> zk: {
>> >>        connect: "localhost:2181”,
>> >> …
>> >> ]]
>> >>
>> >>
>> >> What am I overlooking?
>> >>
>> >> Also, any directions re the rest of my questions (re bin/submit_plan
>> etc.)?
>> >>
>> >>
>> >> With a little help from here,  I’m happy to put together the
>> description
>> >> how to set this up in the Wiki, also to address a query we’ve now lying
>> >> around for more than three weeks, by Steve McPherson – see
>> >>
>> http://mail-archives.apache.org/mod_mbox/incubator-drill-user/201310.mbox/%3CCE71A20F.14F5B%25stevemp%40amazon.com%3E–<http://mail-archives.apache.org/mod_mbox/incubator-drill-user/201310.mbox/%3CCE71A20F.14F5B%25stevemp%40amazon.com%3E%E2%80%93>the fact that it attracted 0 responses I find slightly embarrassing, and
>> >> if I were Steve, I’d prolly not touch Drill anymore, but let’s hope
>> for the
>> >> best …
>> >>
>> >>
>> >> Cheers,
>> >>                Michael
>> >>
>> >> --
>> >> Michael Hausenblas
>> >> Ireland, Europe
>> >> http://mhausenblas.info/
>> >>
>> >>> On 27 Oct 2013, at 21:32, Steven Phillips <[EMAIL PROTECTED]>
>> wrote:
>> >>>
>> >>> One thing to add to the diagram is that all of the drill java
>> processes
>> >>> will look at what is in drill-override.conf. You must set zk.connect
>> to
>> >> the
>> >>> correct zk host:port.
>> >>>
>> >>>
>> >>> On Sun, Oct 27, 2013 at 2:00 PM, Michael Hausenblas <
>> >>> [EMAIL PROTECTED]> wrote:
>> >>>
>> >>>>
>> >>>> Folks,
>> >>>>
>> >>>> I’m trying to set up Drill in distributed mode. Here’s what I have so
>> >> far:
>> >>>> when I launch the first Drillbit with bin/drillbit.sh I get the
>> >> following
>> >>>> in log/drillbit.out:
>> >>>>
>> >>>> [[
>> >>>> 20:47:20.963 [main] ERROR com.netflix.curator.ConnectionState -
>> >> Connection
>> >>>> timed out for connection string (localhost:2181) and timeout (5000) /
>> >>>> elapsed (5045)
>> >>>> org.apache.zookeeper.KeeperException$ConnectionLossException:
>> >>>> KeeperErrorCode = ConnectionLoss
>> >>>>       at
>> >>>>
>> >>
>> com.netflix.curator.ConnectionState.getZooKeeper(ConnectionState.java:94)
>> >>>> ~[curator-client-1.1.9.jar:na]
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB