Le 10/07/2014 18:43, Raúl Gutiérrez Segalés a écrit :
> On 10 July 2014 09:00, Damien Hardy <dha...@viadeoteam.com> wrote:
> 
>> Hello,
>>
>> My question is how can we run with mesos 0.18.0 whereas requirement on
>> zookeeper are on an older version : 3.3.4 (mesos embed 3.4.3).
>>
>> Actually I have problems tring to register on an existing mesos 0.18.2
>> cluster running.
>> When I try to run aurora on an existing cluster I get those logs on
>> zookeeper server (created a gist for readability)
>>   https://gist.github.com/dhardy92/c8a20d1d054b9f05d919
>>
>> And on aurora side ending with:
>> I0710 16:17:18.876508 8952 log.cpp:805] Timed out while trying to get
>> elected
>> E0710 16:17:18.876687  8952 log.cpp:830] Retry limit has been reached
>> during election
>> I0710 16:17:18.877921  8952 log.cpp:849] Attempting to append 5 bytes to
>> the log
>> E0710 16:17:18.878243  8952 log.cpp:866] Failed to append the log: No
>> election has been performed
>>
>> Is there any plan to upgrade zookeeper dependencies ?
>>
> 
> So this is a 3.4 ZK client library talking to a 3.3 ZK server, or the other
> way around? It should work for both combinations, iirc.
> 
> Could you maybe try a small test prog that just connects to the ensemble?
> The log excerpts you shared seem to hint just normal timeouts... (i
> think!).
> 
> 
> -rgs
> 

Hello,

This is aurora zookeeper client (zk 3.3) talking to cdh4.1.2 zookeeper
server (where mesos 0.18.2 is deployed) (zk 3.4.3)

Cheers
-- 
Damien HARDY

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to