Return-Path: X-Original-To: apmail-curator-user-archive@minotaur.apache.org Delivered-To: apmail-curator-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D1D73171D2 for ; Sun, 13 Sep 2015 21:22:54 +0000 (UTC) Received: (qmail 29181 invoked by uid 500); 13 Sep 2015 21:22:54 -0000 Delivered-To: apmail-curator-user-archive@curator.apache.org Received: (qmail 29127 invoked by uid 500); 13 Sep 2015 21:22:54 -0000 Mailing-List: contact user-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@curator.apache.org Delivered-To: mailing list user@curator.apache.org Received: (qmail 29117 invoked by uid 99); 13 Sep 2015 21:22:54 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Sep 2015 21:22:54 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 3D055F1CFE for ; Sun, 13 Sep 2015 21:22:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.899 X-Spam-Level: ** X-Spam-Status: No, score=2.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id fXRrUyt50joO for ; Sun, 13 Sep 2015 21:22:48 +0000 (UTC) Received: from mail-io0-f180.google.com (mail-io0-f180.google.com [209.85.223.180]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 41C1520F5E for ; Sun, 13 Sep 2015 21:22:47 +0000 (UTC) Received: by iofh134 with SMTP id h134so147098440iof.0 for ; Sun, 13 Sep 2015 14:22:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=3oJkCPMInhRExV3rzPlHOo+UD38G/Zg4xQAHTaWdS+g=; b=xLjDR2KqGaEgQ30oIg8p4sfCnpM+TnEZPn74L7n3PCDLYuuL96jPL0u7Ax4hTHCGWm mdIRr4z20pZ3BaV4afv+LwQFSyIiBVMH/BnuQ4CJ4TUam3DgDMB6ULmO+IsFeJYGIr4k lQiqbJgw3IlK2M6tFyvYzT/3S834ugRSdEXw5nq9T0kiI8yxMTpmpu1N41Xh3AbjqnEX MFLaG6OcQP7yVbH9ySK5frebWJoGQ/+oKiINGLaFJKW8xNG2Lt6P9SHnLMVSxvrXDHqh oVqbNw3zImJItqy8gRSCw2TSMsHGolB4uiC7hNLToSnakj0czw6gXRDwom34wc/Ex/jj 7zXA== X-Received: by 10.107.162.136 with SMTP id l130mr4492266ioe.86.1442179366339; Sun, 13 Sep 2015 14:22:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.130.36 with HTTP; Sun, 13 Sep 2015 14:22:26 -0700 (PDT) In-Reply-To: References: <9A39BFC2-601E-47FA-A10A-BA24569DC818@jordanzimmerman.com> From: Check Peck Date: Sun, 13 Sep 2015 14:22:26 -0700 Message-ID: Subject: Re: Best Practice while creating znodes? To: Jordan Zimmerman Cc: user , user Content-Type: multipart/alternative; boundary=001a1141b65ad5494a051fa78c9d --001a1141b65ad5494a051fa78c9d Content-Type: text/plain; charset=UTF-8 Why all client has to set this limit. If on zookeeper side we have configured this then it should use that. No? Also how can we set this parameter through Curator? I don't see any methods in CuratorrFramework which takes this variable. On Sun, Sep 13, 2015 at 2:17 PM, Jordan Zimmerman < jordan@jordanzimmerman.com> wrote: > Yes, all clients. Curator just wraps ZooKeeper so all the same things > apply. > > -Jordan > > > > On September 13, 2015 at 4:14:17 PM, Check Peck (comptechgeeky@gmail.com) > wrote: > > I mean this code for getting children not earlier one, that is for data. > > List children = client.getChildren().forPath(path); > > On Sun, Sep 13, 2015 at 2:10 PM, Check Peck > wrote: > >> Ok understood that part and I was correct on the 500 children nodes znode >> name example right? >> >> If I can increase the jute.maxBuffer property, I do need to restart the >> whole cluster. Correct? Is there any problem if I increase this? >> >> On Sun, Sep 13, 2015 at 2:08 PM, Jordan Zimmerman < >> jordan@jordanzimmerman.com> wrote: >> >>> No, the 1MB limit will hit you there as well. If you try to get your >>> data (via getData() call) it will fail. Note, you can increase the value >>> via the jute.maxBuffer property. >>> >>> -Jordan >>> >>> On September 13, 2015 at 4:06:48 PM, Check Peck (comptechgeeky@gmail.com) >>> wrote: >>> >>> What about data in those znode? They can be more than 1MB in each znode >>> correct? >>> >>> >> > --001a1141b65ad5494a051fa78c9d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Why all client has to set this limit. If on zookeeper= side we have configured this then it should use that. No?

Als= o how can we set this parameter through Curator? I don't see any method= s in CuratorrFramework which takes this variable.

On Sun, Sep 13, 2015 at 2:17 PM, = Jordan Zimmerman <jordan@jordanzimmerman.com> wrote= :
Yes, all clients. Curator just wraps ZooKeepe= r so all the same things apply.

-Jordan



=

On September 13, 2015 at 4:14:17 PM, Check Peck (comptechgeeky@gm= ail.com) wrote:

I mean this code for getting children not earlier one, that is for data.

List<String> children =3D client.getChildren().forPath(path);

On Sun, Sep 13, 2015 at 2:10 PM, Check Peck <comptechgeeky@gmail.com> wrote:
Ok understood that part and I was correct on the 500 children nodes znode name example right?

If I can increase the jute.maxBuffer property, I do need to restart the whole cluster. Correct? Is there any problem if I increase this?

On Sun, Sep 13, 2015 at 2:08 PM, Jordan Zimmerman <jordan@jordanzimmerman.com> wrote:
No, the 1MB limit will hit you there as well. If you try to get your data (via getData() call) it will fail. Note, you can increase the value via the jute.maxBuffer property.

-Jordan

On September 13, 2015 at 4:06:48 PM, Check Peck (co= mptechgeeky@gmail.com) wrote:

What about data in those znode? They can be more than 1MB in each znode correct?




--001a1141b65ad5494a051fa78c9d--