Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 97302 invoked from network); 25 Jan 2010 07:06:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Jan 2010 07:06:04 -0000 Received: (qmail 69519 invoked by uid 500); 25 Jan 2010 07:06:04 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 69468 invoked by uid 500); 25 Jan 2010 07:06:03 -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 69458 invoked by uid 99); 25 Jan 2010 07:06:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 07:06:03 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of qingyan@gmail.com designates 209.85.221.203 as permitted sender) Received: from [209.85.221.203] (HELO mail-qy0-f203.google.com) (209.85.221.203) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 07:05:56 +0000 Received: by qyk41 with SMTP id 41so2181041qyk.29 for ; Sun, 24 Jan 2010 23:05:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=imKcRJUJklR3MeiiNnK+ERNp9v+eDqNSM1o+ayHj5aE=; b=Y4/4GHhCEiYqK+gv3VZWOHszz53mZmWfMEmbCi2Ag4Kg+mAWVvUtP+WVx4L20Cn9mG L3rMiLkjFNL5eSEZYQp6fXnk3Er4xLPPbVl6rnQf8DilgbFLXacdlqnx6otmp2OR1w9o IQE+r/Wy9CFoUB6Mjjft/BrlNgAEhx8hCGxpM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=TXMLn1ZTdnG2QJRdRvkf2fzcMrSeaVbJ2lqXPTnNXFfQnsYjdREYvd+xzQERAr5dLo vv+NnN8VmF1C9yX0TqDT0qZiQGplItIeDTVXfeuwMAASEDdStr/s20dUJk27BkUO6kdj raq6dqFPGb3cF7UEc6WgyWKnB2SAnH948ElIM= MIME-Version: 1.0 Received: by 10.220.124.87 with SMTP id t23mr493300vcr.104.1264403135286; Sun, 24 Jan 2010 23:05:35 -0800 (PST) In-Reply-To: References: <34fd060d1001230058ybeca0b1n79bdcd97e63be76@mail.gmail.com> <34fd060d1001242109k3f735a61y845b0a932bb43773@mail.gmail.com> Date: Mon, 25 Jan 2010 15:05:35 +0800 Message-ID: Subject: Re: Using zookeeper to assign a bunch of long-running tasks to nodes (without unhandled tasks and double-handled tasks) From: Qing Yan To: zookeeper-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001636d34426bb5015047df7cb70 --001636d34426bb5015047df7cb70 Content-Type: text/plain; charset=ISO-8859-1 Hi guys, Let me ask a design/best practice question. The design you guys are talking about seems to be p2p based, under what circumstances is such design prefered to a master-based one(like gfs,bigtable,hbase...)? Looks like for a full fledged system,a master is needed anyway to carry out bookkeeping activities, not mention it is simple to design(no race condition,herd effect etc). BTW is it a good practice to store indivdual node's monitoring metrics inside Zookeeper with proactive refreshing(say every sec)? Is this considered as abuse? --001636d34426bb5015047df7cb70--