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 1F74F10774 for ; Tue, 2 Jul 2013 03:38:24 +0000 (UTC) Received: (qmail 69927 invoked by uid 500); 2 Jul 2013 03:38:23 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 69901 invoked by uid 500); 2 Jul 2013 03:38:22 -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 69892 invoked by uid 99); 2 Jul 2013 03:38:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 03:38:21 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ted.dunning@gmail.com designates 209.85.160.41 as permitted sender) Received: from [209.85.160.41] (HELO mail-pb0-f41.google.com) (209.85.160.41) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 03:38:14 +0000 Received: by mail-pb0-f41.google.com with SMTP id rp16so5633510pbb.14 for ; Mon, 01 Jul 2013 20:37:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=nOxTcVHvsph5WZL7ImnHTwMwe8h2lJNWdjVmCIlSCWc=; b=Drdfb2BSfRsifGqYQNviLaT5kjpE02wGna9LmeUCyRs040iBmUtsBOok/akK8RmZxE EjNzoRUWIlreiGXpE7G2M5a+7RivRiDwJRvy5MADS1DM4jLHZJe7nY5eIegjbdFvpPyE VPw0eFis7QUV9kxdemwYuaCN+bGjpJCMnIQYDzu4BeUkNmrt8DhGWnpBRI5Ql/6WDLfX wBNtvdr6eQy4c1H6/A6bK78qgVYy7X69+mGJmDWYeKLE6z5UXt9GYEW2WB7P9ofgP5AQ y2kxFu04B/ICQ3ytYlL41zXrLwXbY23l99oK3nJj8+FFZ3UrRDR3iU/JvuE9ga77/jXT xdPQ== X-Received: by 10.68.192.103 with SMTP id hf7mr26973569pbc.168.1372736272630; Mon, 01 Jul 2013 20:37:52 -0700 (PDT) Received: from [10.149.14.199] (mobile-166-137-212-142.mycingular.net. [166.137.212.142]) by mx.google.com with ESMTPSA id pb5sm25155777pbc.29.2013.07.01.20.37.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 20:37:50 -0700 (PDT) References: <316f0048.f2f7.13f9d583b11.Coremail.qhwj2006@126.com> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: <1EC6F53E-C1B0-4DFD-BF24-AC3B961CED98@gmail.com> Cc: "user@zookeeper.apache.org" X-Mailer: iPhone Mail (10A523) From: Ted Dunning Subject: Re: Is it a good idea to embed ZK in a product application ? Date: Mon, 1 Jul 2013 20:37:47 -0700 To: "user@zookeeper.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org Embedding zk in a product is a fine thing. Embedding zk in an application i= s (in my estimation) a bad idea. The problem is that you generally want to c= oordinate all the way down to zero, especially in upgrade situations. Combi= ning the uptime constraints of zk with those of your app is bad strategy. =20= As a concrete example, suppose that you need one or more copy if your softwa= re to run and you are running it on 6 machines. Should your zk quorum inclu= de all 6 machines? I think not. =20 Now what happens if you want to upgrade? It is plausible that your app will= work with only or copy running but you probably would want enough to handle= current load during a rolling upgrade. Should that requirement be combined= with the need to preserve a zk quorum? What if you have zk on 3 machines a= nd you want to upgrade all three of those in step 1 of a rolling upgrade. D= o you really want to make that impossible? Sent from my iPhone On Jul 1, 2013, at 20:22, Kai Lu wrote: > A lot of applications in big companies had done that already. >=20 > On Jul 1, 2013, at 8:06 PM, =E5=90=B4=E9=9D=96 wrote: >=20 >> Hi all: >>=20 >>=20 >> Recently my company want use zk to manage our cluster( For node manageme= nt and HA). But someone in my team want to embed the ZK in our product appli= cation. But somehow I always feel very odd to embed ZK in. >> Here my question are : Is it a good idea to embed ZK in a product appli= cation ? >> And dose it work fine in product mode (like overflow memory and othe= r problems )? >>=20 >>=20 >>=20 >> thank you ! >>=20 >>=20