curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Jaton <benjamin.ja...@gmail.com>
Subject Re: Curator and ReadOnly
Date Wed, 23 Nov 2016 21:41:01 GMT
I'm sorry I am using Curator 3.2.1 (not 2.7.1)

On Wed, Nov 23, 2016 at 1:39 PM, Benjamin Jaton <benjamin.jaton@gmail.com>
wrote:

> Sure, I'm using Curator 2.7.1 and ZK 3.5.2-alpha.
> I do set readonlymode.enabled in the code.
>
> Thanks
> Benjamin
>
> On Wed, Nov 23, 2016 at 1:15 PM, Vadim <vadim@ant.ee> wrote:
>
>> Benjamin,
>>
>>       Can you specify Zookeeper version you use and whether you set up "
>> *readonlymode.enabled*" to true? By default read-only mode for ZK server
>> is disabled.
>>
>> Vadim.
>>
>>
>>
>>
>> On 2016-11-23 22:03, Benjamin Jaton wrote:
>>
>> Hello,
>>
>> Before I open a new JIRA for this, I wanted to bring it up here first.
>>
>> Basically the issue I'm seeing is that the read requests fail when
>> connecting to a read only ensemble.
>>
>> I made a test for this using TestingCluster, but it requires to set
>> iptables rules in order to mimic a real (remote) read-only ensemble. The
>> test will do this:
>> 1) start a TestingCluster
>> 2) stop 2 of the 3 nodes
>> 3) user has to run the iptables commands (specified in the logs)
>> 4) a read request is issued every 3 seconds
>>
>> All the read requests block for approx 2 minutes, then they all throw an
>> exception (ConnectionLoss).
>>
>> I was wondering if other users were using Curator with a read only
>> ensemble?
>>
>> Thanks
>> Benjamin
>>
>>
>

Mime
View raw message