zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Flavio Junqueira <fpjunque...@yahoo.com.INVALID>
Subject Re: Asynchronous API's and monotonicity
Date Fri, 06 Jun 2014 21:19:07 GMT
There are ways around this. You can create a hierarchy to get around the problems you're talking
about, like we did with the hierarchical ledger manager in bookkeeper. But granted, if all
you want to do is a queue, perhaps there are better options out there.

-Flavio

On 06 Jun 2014, at 22:11, Diego Oliveira <lokimad@gmail.com> wrote:

> Flavio,
> 
>   Queues usually may have a lot of messages and you may use a znode to
> keep those messages. When the client want to list the messages in a anode
> the Zookeeper server must pass the child names, but there is a data
> transportation limit between the server and the client and if the child
> names is larger then this limit the queue crashes. I got this problem in a
> production system. Take a look for more details the curator wiki (
> https://github.com/Netflix/curator/wiki/Tech-Note-4).
> 
> 
> 
> 
> On Fri, Jun 6, 2014 at 6:04 PM, Flavio Junqueira <
> fpjunqueira@yahoo.com.invalid> wrote:
> 
>> I don't quite understand the correlation among amount of data per znode,
>> queues, and being a well known problem. You might as well be right, though.
>> 
>> -Flavio
>> 
>> On 06 Jun 2014, at 21:25, Diego Oliveira <lokimad@gmail.com> wrote:
>> 
>>> Mudit,
>>> 
>>>   Just to let you know, Zookeeper isn't the best choice for queue, it
>> has
>>> problems in the amount of data that a anode can handle. It is a very well
>>> know problem.
>>> 
>>> Att,
>>>    Diego
>>> 
>>> 
>>> On Fri, Jun 6, 2014 at 5:12 AM, Mudit Verma <mudit.f2004912@gmail.com>
>>> wrote:
>>> 
>>>> Thanks James and Rakesh. It helps :)
>>>> 
>>>> On 05 Jun 2014, at 21:07, James A. Robinson <jimr@highwire.org> wrote:
>>>> 
>>>>> On Thu, Jun 5, 2014 at 9:45 AM, Rakesh Radhakrishnan <
>>>> rakeshr.apache@gmail.com> wrote:
>>>>> But this behaviour may not be same if we perform operations through
>>>>> different clients. Here network delays or other factors may cause
>>>> different
>>>>> clients to see a change.
>>>>> 
>>>>> I'm assuming the other important factor is to ensure that he's
>>>>> either got a single control loop dispatching the async calls to
>>>>> his zookeeper connection or that he's coordinating the threads
>>>>> himself to impose ordering.
>>>>> 
>>>>> Otherwise, if one has threads x1 and x2 running in parallel,
>>>>> he'd have no guarantee which thread dispatched its async
>>>>> call to zookeeper first.
>>>>> 
>>>>> Jim
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> Att.
>>> Diego de Oliveira
>>> System Architect
>>> diego@diegooliveira.com
>>> www.diegooliveira.com
>>> Never argue with a fool -- people might not be able to tell the
>> difference
>> 
>> 
> 
> 
> -- 
> Att.
> Diego de Oliveira
> System Architect
> diego@diegooliveira.com
> www.diegooliveira.com
> Never argue with a fool -- people might not be able to tell the difference


Mime
View raw message