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 Plain View
Drill >> mail # dev >> Re: Distributed mode troubles: ZK/Curator connection time out


Copy link to this message
-
Re: Distributed mode troubles: ZK/Curator connection time out
Zk is (or was) a bit delicate in the case of failure to resolve addresses.  That might be the cause here.  

Sent from my iPhone

On Oct 28, 2013, at 16:15, Jacques Nadeau <[EMAIL PROTECTED]> wrote:

> I seem to recall issues right now if you're not connected to the internet.
> Can you do some testing to see whether that was the problem you were
> having?
>
> Thanks,
> Jacques
>
>
> On Mon, Oct 28, 2013 at 2:42 AM, Michael Hausenblas <
> [EMAIL PROTECTED]> wrote:
>
>>
>> Interestingly enough now it works. Can it be that due to whatever reasons
>> there must be an Internet connection available?. BTW, I’m doing the stuff
>> on MacOS 10.9.
>>
>> $ bin/submit_plan -f sample-data/physical_json_scan_test1.json -t physical
>> -zk 127.0.0.1:2181
>>
>>
>> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>> | id             | type           | name           | ppu            |
>> sales          | batters.batter.id| batters.batter.type| topping.id     |
>> topping.type   | filling.id     | filling.type   |
>>
>> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>> | 0001           | donut          | Cake           | 0.55           | 35
>>
>>
>> Still, strangely enough there are errors in submitter.log (that do not
>> affect the result, but would love to understand what’s going on here):
>>
>> [[
>>
>> 09:37:20.632 [Client-1] DEBUG o.a.d.e.rpc.user.QueryResultHandler -
>> Received QueryId part1: 3952191315122866480
>> part2: -6119095990164217550
>> succesfully.  Adding listener
>> org.apache.drill.exec.client.QuerySubmitter$QueryResultsListener@1d007a1a
>> 09:37:27.005 [Client-1] ERROR o.a.d.exec.rpc.RpcExceptionHandler -
>> Exception in pipeline.  Closing channel between local /10.109.7.56:63536and remote /
>> 10.109.7.56:31012
>> io.netty.handler.codec.DecoderException:
>> java.lang.IndexOutOfBoundsException
>>        at
>> io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:99)
>> [netty-codec-4.0.7.Final.jar:na]
>>        at
>> io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:334)
>> [netty-transport-4.0.7.Final.jar:na]
>>        at
>> io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:320)
>> [netty-transport-4.0.7.Final.jar:na]
>>        at
>> io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
>> [netty-codec-4.0.7.Final.jar:na]
>>        at
>> io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:334)
>> [netty-transport-4.0.7.Final.jar:na]
>>        at
>> io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:320)
>> [netty-transport-4.0.7.Final.jar:na]
>>        at
>> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:173)
>> [netty-codec-4.0.7.Final.jar:na]
>>        at
>> io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:334)
>> [netty-transport-4.0.7.Final.jar:na]
>>        at
>> io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:320)
>> [netty-transport-4.0.7.Final.jar:na]
>>        at
>> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785)
>> [netty-transport-4.0.7.Final.jar:na]
>>        at
>> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:100)
>> [netty-transport-4.0.7.Final.jar:na]
>>        at
>> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:497)
>> [netty-transport-4.0.7.Final.jar:na]
>>        at
>> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:465)
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