I found there is a
System.setProperty("zookeeper.forceSync", "no");
but this just seem to lead to other problems down the road.
On Tue, Dec 16, 2014 at 2:00 PM, Ernesto Reinaldo Barreiro <
[email protected]> wrote:
>
> I'm new to storm but I was able to get rid of that by giving more memory
> to my local cluster.
>
> On Tue, Dec 16, 2014 at 1:53 PM, Denis DEBARBIEUX <[email protected]>
> wrote:
>>
>> Dear all,
>>
>> I am a new user of storm. I am writing a proof of concept with a very
>> simple topology.
>> I am using the local mode. When I run my application during 5 minutes, it
>> is OK. But I am not able to run it during hours. Indeed, it always fails
>> and stops with the following error (I enclosed the full stack strace):
>>
>> WARN org.apache.storm.zookeeper.server.persistence.FileTxnLog -
>> fsync-ing the write ahead log in SyncThread:0 took 4702ms which will
>> adversely effect operation latency. See the ZooKeeper troubleshooting guide
>>
>> (...)
>>
>> org.apache.zookeeper.server.NIOServerCnxn - caught end of stream
>> exception
>> org.apache.zookeeper.server.ServerCnxn$EndOfStreamException: Unable to
>> read additional data from client sessionid 0x14a526c861a0003, likely client
>> has closed socket
>>
>> (...)
>>
>> java.nio.channels.CancelledKeyException: null
>> at
>> sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:73)
>>
>> (...)
>>
>> There is a reference to ZooKeeper troubleshooting guide. But I do not
>> find any solution/workaround in it.
>>
>> It looks like a problem in the logger of ZooKeeper. Is-it possible de
>> disable it?
>>
>> Any help is welcome.
>>
>> *Denis DEBARBIEUX*
>> norsysgroupe
>>
>>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>
--
Regards - Ernesto Reinaldo Barreiro
