Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: domain of fpjunqueira@yahoo.com
 designates 212.82.96.69 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Subject: Re: Asynchronous API's and monotonicity
From: Flavio Junqueira <fpjunqueira@yahoo.com.INVALID>
In-Reply-To: 
 <CAFOSzKGREvj5pqm+mNPCrGKcrZO17XcaC-iAK9wTavvwxh4r3g@mail.gmail.com>
Date: Fri, 6 Jun 2014 22:19:07 +0100
Cc: "James A. Robinson" <jimr@highwire.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DCA6EE7D-BC17-467D-9570-7E65666E0859@yahoo.com>
References: <5309FE79-A579-4604-A82C-EF993AFD8459@gmail.com>
 <CAHB_t6qSh31pX3rXvN2mjBNS0Ak09qspdgcmie079jEvnEqanQ@mail.gmail.com>
 <CAPd04b5h_Vmq6=w7wYv8nOphjVQrr98SxvXkxKJPoWejfUGu7w@mail.gmail.com>
 <8BA266F0-4A62-4550-B5A5-BB791198BE72@gmail.com>
 <CAFOSzKFRdABbS8DXMOMOG1Vy1PMMVEMzkwfrmT=9bR6mLNKgFA@mail.gmail.com>
 <08584CB7-2C7A-43CF-BC5A-7DD62978C5CF@yahoo.com>
 <CAFOSzKGREvj5pqm+mNPCrGKcrZO17XcaC-iAK9wTavvwxh4r3g@mail.gmail.com>
To: user@zookeeper.apache.org

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,
>=20
>   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).
>=20
>=20
>=20
>=20
> On Fri, Jun 6, 2014 at 6:04 PM, Flavio Junqueira <
> fpjunqueira@yahoo.com.invalid> wrote:
>=20
>> 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.
>>=20
>> -Flavio
>>=20
>> On 06 Jun 2014, at 21:25, Diego Oliveira <lokimad@gmail.com> wrote:
>>=20
>>> Mudit,
>>>=20
>>>   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.
>>>=20
>>> Att,
>>>    Diego
>>>=20
>>>=20
>>> On Fri, Jun 6, 2014 at 5:12 AM, Mudit Verma =
<mudit.f2004912@gmail.com>
>>> wrote:
>>>=20
>>>> Thanks James and Rakesh. It helps :)
>>>>=20
>>>> On 05 Jun 2014, at 21:07, James A. Robinson <jimr@highwire.org> =
wrote:
>>>>=20
>>>>> 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.
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>> Jim
>>>>>=20
>>>>=20
>>>>=20
>>>=20
>>>=20
>>> --
>>> 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
>>=20
>>=20
>=20
>=20
> --=20
> 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