Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BD20DC509 for ; Wed, 16 May 2012 19:46:37 +0000 (UTC) Received: (qmail 58578 invoked by uid 500); 16 May 2012 19:46:37 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 58552 invoked by uid 500); 16 May 2012 19:46:37 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 58542 invoked by uid 99); 16 May 2012 19:46:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 19:46:37 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [213.199.154.144] (HELO db3outboundpool.messaging.microsoft.com) (213.199.154.144) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 19:46:31 +0000 Received: from mail81-db3-R.bigfish.com (10.3.81.248) by DB3EHSOBE003.bigfish.com (10.3.84.23) with Microsoft SMTP Server id 14.1.225.23; Wed, 16 May 2012 19:46:02 +0000 Received: from mail81-db3 (localhost [127.0.0.1]) by mail81-db3-R.bigfish.com (Postfix) with ESMTP id 202423E0379 for ; Wed, 16 May 2012 19:46:02 +0000 (UTC) X-SpamScore: -16 X-BigFish: VPS-16(zz9371I542M1432N98dK4015Izz1202hzz8275bh8275dhz2dh2a8h668h839h8aah944hd25h) X-Forefront-Antispam-Report: CIP:64.132.13.29;KIP:(null);UIP:(null);SRV:BULK;H:PVSWMAIL2.pervasive.com;RD:64-132-13-29.static.twtelecom.net;EFVD:NLI Received: from mail81-db3 (localhost.localdomain [127.0.0.1]) by mail81-db3 (MessageSwitch) id 1337197560251846_6751; Wed, 16 May 2012 19:46:00 +0000 (UTC) Received: from DB3EHSMHS018.bigfish.com (unknown [10.3.81.236]) by mail81-db3.bigfish.com (Postfix) with ESMTP id 3950834006F for ; Wed, 16 May 2012 19:46:00 +0000 (UTC) Received: from PVSWMAIL2.pervasive.com (64.132.13.29) by DB3EHSMHS018.bigfish.com (10.3.87.118) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 16 May 2012 19:45:58 +0000 Received: from PVSWMAIL2010.pervasive.com ([::1]) by PVSWMAIL2.pervasive.com ([::1]) with mapi id 14.02.0283.003; Wed, 16 May 2012 14:46:03 -0500 From: Narasimha Tadepalli To: "user@zookeeper.apache.org" Subject: RE: Distribution Problems With Multiple Zookeeper Clients Thread-Topic: Distribution Problems With Multiple Zookeeper Clients Thread-Index: Ac0ywDG2tkRtbLhwQ3qbSc1RKiP47QAMRlCAACqnMtA= Date: Wed, 16 May 2012 19:46:02 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.5.24] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: pervasive.com X-Virus-Checked: Checked by ClamAV on apache.org Hi Camille Sorry for the confusion. Yes it is watches. We have multiple clients config= ured to watch on event change at server end. For example we have a data dir= ectory of /data/345/text. All 30 clients keep watching for event change und= er /data/345 directory if there is any change clients need to process and r= ead the child nodes. In this situation not all clients not getting equal ev= ents. I am looking for a way to distribute the load equally to all client i= nstances. I hope I provided enough clarification now or else let me know. Thanks Narasimha -----Original Message----- From: cf@renttherunway.com [mailto:cf@renttherunway.com] On Behalf Of Camil= le Fournier Sent: Tuesday, May 15, 2012 1:20 PM To: user@zookeeper.apache.org Subject: Re: Distribution Problems With Multiple Zookeeper Clients I'm not sure what you mean by messages. Are you talking about watches? Can = you describe your clients in more detail? Thanks, Camille On Tue, May 15, 2012 at 1:29 PM, Narasimha Tadepalli < Narasimha.Tadepalli@= pervasive.com> wrote: > Dear All > > We have a situation where messages are not distributed equally when we=20 > have multiple clients listening to one zookeeper cluster. Say we have=20 > 30 client instances listing to one cluster and when 1000 messages=20 > submitted in > 30 mins to cluster I assume each client approximately supposed to=20 > receive > 33 messages. But out of 30 only 10 client instances taking max load=20 > and rest of them getting very low volume of messages. Is it something=20 > can be configurable in zookeeper settings or need to implement some=20 > custom solution at our end to distribute equally? Before I reinvent=20 > the wheel looking around for some suggestions if any of you faced similar= situation. > > Thanks > Narasimha > >