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 5D73310FCA for ; Thu, 7 Nov 2013 23:31:43 +0000 (UTC) Received: (qmail 24653 invoked by uid 500); 7 Nov 2013 23:31:42 -0000 Delivered-To: apmail-curator-user-archive@curator.apache.org Received: (qmail 24602 invoked by uid 500); 7 Nov 2013 23:31:42 -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 24530 invoked by uid 99); 7 Nov 2013 23:31:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Nov 2013 23:31:42 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.192.169] (HELO mail-pd0-f169.google.com) (209.85.192.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Nov 2013 23:31:35 +0000 Received: by mail-pd0-f169.google.com with SMTP id q10so1302793pdj.28 for ; Thu, 07 Nov 2013 15:31:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=ys/4Z1ah3a2b5p8ATQs51p5E9HA7i4ZJHefk3Ks7a0Y=; b=W5O0IAU+lMTzof/0WT8mWprrF0zTRtQWSemcmsUBL9+loJVzvnGYH7XleGCydNbNEe VqTWYnzFLMwDfapEJgtHagCXm6ZFSC6da7VcVBm27hYC+pJti8RHfjq9eBMzWbntpqjr 3zF+G2gFs5QWIMkfpYMR7xB5AhzWx6cmInlTZlLYx65Ifp8jUGHu6UReBx5rRqX+0lcB HLe7n6Y4MF/k6btnhILwLbp58vAfgfXUNMqpYQCu+cXiWhY70RbPNU72kX2i4muoOAj5 QKzOhq2H3HPZJ4QT1HQRSUz2YnfLjQ3rSNxY/G1ZDN/ZEU5z33WRjAWylWJK9xoGziYs yPTg== X-Gm-Message-State: ALoCoQnF2/8JVl9gLCLNYqRuWV9jphga7ZvroDPNzyWXTA/S6uI7XBQMB1zF8xdznJ1tptAQLoUH X-Received: by 10.67.11.103 with SMTP id eh7mr12420225pad.153.1383867073945; Thu, 07 Nov 2013 15:31:13 -0800 (PST) Received: from [10.0.0.11] (c-50-168-88-247.hsd1.ca.comcast.net. [50.168.88.247]) by mx.google.com with ESMTPSA id ye1sm9296971pab.19.2013.11.07.15.31.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 07 Nov 2013 15:31:13 -0800 (PST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: Best Practice while creating znodes? From: Jordan Zimmerman In-Reply-To: Date: Thu, 7 Nov 2013 15:31:11 -0800 Cc: user Content-Transfer-Encoding: quoted-printable Message-Id: References: <9A39BFC2-601E-47FA-A10A-BA24569DC818@jordanzimmerman.com> To: user@zookeeper.apache.org X-Mailer: Apple Mail (2.1510) X-Virus-Checked: Checked by ClamAV on apache.org Totally up to you. On Nov 7, 2013, at 2:54 PM, Techy Teck wrote: > Sure.. Thanks for the help.. >=20 > Apart from that like, znodes name should be small? Is that the case as > well? Or it doesn't matter if it is long as well? >=20 >=20 > On Thu, Nov 7, 2013 at 10:57 AM, Jordan Zimmerman < > jordan@jordanzimmerman.com> wrote: >=20 >> There are very few limitations on naming. You can't use a slash. Have = a >> look at: >>=20 >> org.apache.zookeeper.common.PathUtils >>=20 >> In terms of length, ZooKeeper has a 1MB limit per API call. So, for >> example, if you call getChildren(), the entire length of all the = children >> can't exceed 1MB (unless you reconfigure ZK). >>=20 >> -JZ >>=20 >> On Nov 7, 2013, at 10:45 AM, Techy Teck = wrote: >>=20 >> Can anyone help me on this? >>=20 >> Is there any best practices that we need to follow while creating the >> znodes? >>=20 >> Meaning the znode name should be small not very large names or there >> shouldn't be a dot or underscore within the word? >>=20 >> Anything like that? >>=20 >> I will be using Apache Curator. >>=20 >>=20 >>=20 >>=20 >> On Wed, Nov 6, 2013 at 11:24 AM, Techy Teck = wrote: >>=20 >>> Is there any best practices that we need to follow while creating = the >>> znodes? >>>=20 >>> Meaning the znode name should be small not very large names or there >>> shouldn't be a dot or underscore within the word? >>>=20 >>> Anything like that? >>>=20 >>>=20 >>=20 >>=20