Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 52523 invoked from network); 30 Jun 2010 16:38:44 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Jun 2010 16:38:44 -0000 Received: (qmail 58648 invoked by uid 500); 30 Jun 2010 16:38:44 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 58614 invoked by uid 500); 30 Jun 2010 16:38:43 -0000 Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zookeeper-user@hadoop.apache.org Delivered-To: mailing list zookeeper-user@hadoop.apache.org Received: (qmail 58606 invoked by uid 99); 30 Jun 2010 16:38:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jun 2010 16:38:43 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ted.dunning@gmail.com designates 209.85.161.176 as permitted sender) Received: from [209.85.161.176] (HELO mail-gx0-f176.google.com) (209.85.161.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jun 2010 16:38:36 +0000 Received: by gxk10 with SMTP id 10so850631gxk.35 for ; Wed, 30 Jun 2010 09:37:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=UIo/+Kl/qPy16vxth0LfFoG9wgvrlG0CX92SRfCw6Mg=; b=KGLgg2kVrVvgTFrwJrA2OmXgozYPyvmUs8GvaffakX+D5iS2t8UuFYSJLZFejPmCMF dlSq2h28oiuMzmGdEglAJAYZiMlwkPNSoiwwRBx6CHj9uIfZFzMKhkiew3U347YDlYLV +zpZ7dydWYAVuX1LwLaGOu+wSnDl9vt5JIsnw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=jjQ7GnhHkz4ig9FoxB0O/8453EfFcepKT3m+GX2RZ83BVEo/6D1L88eUNgKUnGU7ny iR8tzmcLNgDbSyjnlZeylzJ6TH/Fm20km4s4jIvWCPKput9uOHw7gbNdd8exwOFiDI57 KQWuLaNIKEpLL8mK0c1nV9p7myGVrGGz5Krco= Received: by 10.224.27.18 with SMTP id g18mr6412024qac.28.1277915846415; Wed, 30 Jun 2010 09:37:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.45.80 with HTTP; Wed, 30 Jun 2010 09:37:06 -0700 (PDT) In-Reply-To: References: From: Ted Dunning Date: Wed, 30 Jun 2010 09:37:06 -0700 Message-ID: Subject: Re: Guaranteed message delivery until session timeout? To: zookeeper-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=00c09f88ceb01415ab048a41f892 X-Virus-Checked: Checked by ClamAV on apache.org --00c09f88ceb01415ab048a41f892 Content-Type: text/plain; charset=UTF-8 Which API are you talking about? C? I think that the difference between connection loss and session expiration might mess you up slightly in your disjunction here. On Wed, Jun 30, 2010 at 7:45 AM, Bryan Thompson wrote: > Hello, > > I am wondering what guarantees (if any) zookeeper provides for reliable > messaging for operation return codes up to a session timeout. Basically, I > would like to know whether a zookeeper client can rely on observing the > return code for a successful operation which creates an ephemeral (or > ephemeral sequential) znode -or- have a guarantee that its session was timed > out and the ephemeral znode destroyed. That is, does zookeeper provide > guaranteed delivery of the operation return code unless the session is > invalidated by a timeout? > > Thanks, > Bryan > --00c09f88ceb01415ab048a41f892--