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 A5364E76D for ; Fri, 1 Mar 2013 21:50:53 +0000 (UTC) Received: (qmail 16947 invoked by uid 500); 1 Mar 2013 21:50:52 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 16864 invoked by uid 500); 1 Mar 2013 21:50:52 -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 16856 invoked by uid 99); 1 Mar 2013 21:50:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Mar 2013 21:50:52 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bitanarch@gmail.com designates 209.85.223.175 as permitted sender) Received: from [209.85.223.175] (HELO mail-ie0-f175.google.com) (209.85.223.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Mar 2013 21:50:46 +0000 Received: by mail-ie0-f175.google.com with SMTP id c12so4176948ieb.34 for ; Fri, 01 Mar 2013 13:50:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=8al0SKR+1RdPadQZ3rmapMB1UkrxELo7/t9A7N/A7rs=; b=bUjg8fpY8uY/cX5wdnwRVhGluC7Np+mrgRkfUHKbWhxTLSRByJDoi1A4t9I7JN4NZ1 F3IlHB6V+HgfPYJLeqWQFQXedqJkP8zs6BcwoffnGkd7vYLePEoA84KUuZElkI2GIa7L QA/6ZkwgXA1EA2qKMWfVo5rj+XM4GZYaGllzFVyC1tGVa7rlF2zKLfTB/lqfFCtoE7ZM fPH9UAvq443Soh6gN9y1sWRaku/QRNyKlXbp08Kqox1f0WlDa465O7Q0W8tBFqEUKi9C li/NnKtUKItt1Dz+8Lqya86D11488TypxoLh9DsCKQSjdrPy+1uBCpggd0wO+bggyo85 Itxw== MIME-Version: 1.0 X-Received: by 10.42.58.67 with SMTP id g3mr7965023ich.56.1362174625935; Fri, 01 Mar 2013 13:50:25 -0800 (PST) Received: by 10.50.30.232 with HTTP; Fri, 1 Mar 2013 13:50:25 -0800 (PST) In-Reply-To: <1362173931985-7578542.post@n2.nabble.com> References: <1362094516049-7578531.post@n2.nabble.com> <1362171044682-7578540.post@n2.nabble.com> <1362173931985-7578542.post@n2.nabble.com> Date: Fri, 1 Mar 2013 13:50:25 -0800 Message-ID: Subject: Re: Consistency in zookeeper From: Martin Kou To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=20cf30334c47b37c3704d6e3fe97 X-Virus-Checked: Checked by ClamAV on apache.org --20cf30334c47b37c3704d6e3fe97 Content-Type: text/plain; charset=ISO-8859-1 Yasin, If the two clients are connected to two different ZooKeeper servers in the cluster, then, yes. Generally, if you're worried that there may be another client working on the same key path, then you should sync() before reading. Best Regards, Martin Kou On Fri, Mar 1, 2013 at 1:38 PM, Yasin wrote: > So, if the read request is made by some other client, it will not get the > updated value without sync, right? > > > > -- > View this message in context: > http://zookeeper-user.578899.n2.nabble.com/Consistency-in-zookeeper-tp7578531p7578542.html > Sent from the zookeeper-user mailing list archive at Nabble.com. > --20cf30334c47b37c3704d6e3fe97--