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 548F710044 for ; Tue, 6 Jan 2015 23:51:52 +0000 (UTC) Received: (qmail 89203 invoked by uid 500); 6 Jan 2015 23:51:52 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 89156 invoked by uid 500); 6 Jan 2015 23:51: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 89142 invoked by uid 99); 6 Jan 2015 23:51:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jan 2015 23:51:51 +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 (nike.apache.org: domain of shralex@gmail.com designates 209.85.216.179 as permitted sender) Received: from [209.85.216.179] (HELO mail-qc0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jan 2015 23:51:27 +0000 Received: by mail-qc0-f179.google.com with SMTP id c9so206579qcz.38 for ; Tue, 06 Jan 2015 15:49:10 -0800 (PST) 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=/rUtyuMniOHENimO+mx65NtayjXJ35McXuaTzTWEURc=; b=FU1gnsGSekCrKhRaOHDTuCvrmw2RrPHGLTCO7DoKoILqT4ePKiZLmGJDaJIyx5Am3Y pyypHTVV2xsCShJoS+1/FGvq9JBM0+0zorqUEeJis2dJN0WSG7pQnNwzqWUECa7NjNL5 3Jtw2nxNVS3rjmAYcKp87pGAVVALW6iNaAu24Zs/AhUM1VMMafYyO2qz8iGteydDTP13 18fSMmVJE25Ed07tTtc8ZzObbZAOtS4mH8AInDVReIY6mEYFJYAZAjXGMiIa/rKElpch ft9ZGIjjskWmwTYpCF73Vax7hw3SvI7llhKk6UIBdOa1WCvaDfICmhjt6xxsKUT+Zy0F h+gQ== X-Received: by 10.140.34.67 with SMTP id k61mr137949405qgk.95.1420588150563; Tue, 06 Jan 2015 15:49:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.242.23 with HTTP; Tue, 6 Jan 2015 15:48:50 -0800 (PST) In-Reply-To: <1420587767194-7580739.post@n2.nabble.com> References: <2015010515052731525120@163.com> <1420576908112-7580736.post@n2.nabble.com> <1420587767194-7580739.post@n2.nabble.com> From: Alexander Shraer Date: Tue, 6 Jan 2015 15:48:50 -0800 Message-ID: Subject: Re: Question about the two-phrase commit To: "user@zookeeper.apache.org" Cc: "zookeeper-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=001a11c0dd5c1628b5050c04746e X-Virus-Checked: Checked by ClamAV on apache.org --001a11c0dd5c1628b5050c04746e Content-Type: text/plain; charset=UTF-8 Yes, if the leader has this operation in its log (not guaranteed if it wasn't acked by majority in previous ensemble, but possible), the leader will make sure that a quorum of followers in the new ensemble has this operation before doing anything else in the new ensemble. Alex On Tue, Jan 6, 2015 at 3:42 PM, Ibrahim wrote: > Hi Alexander, > > So, you meant that if there is operation loged to the disk but it hasn't > got > enough majority, then if the zookeeper servers restart, the new leader will > re-broadcast the loged operation again to the followers to commit that > operation. > > Does above what you meant by (NEWLEADER message acts as the accept and > UPTODATE message acts as commit). > > Am I right? > > Thank you > > Ibrahim > > > > -- > View this message in context: > http://zookeeper-user.578899.n2.nabble.com/Question-about-the-two-phrase-commit-tp7580725p7580739.html > Sent from the zookeeper-user mailing list archive at Nabble.com. > --001a11c0dd5c1628b5050c04746e--