Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 38720 invoked from network); 20 Oct 2009 17:34:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Oct 2009 17:34:49 -0000 Received: (qmail 64024 invoked by uid 500); 20 Oct 2009 17:34:48 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 64007 invoked by uid 500); 20 Oct 2009 17:34:48 -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 63997 invoked by uid 99); 20 Oct 2009 17:34:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Oct 2009 17:34:48 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [69.147.107.20] (HELO mrout1-b.corp.re1.yahoo.com) (69.147.107.20) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Oct 2009 17:34:37 +0000 Received: from SNV-EXBH01.ds.corp.yahoo.com (snv-exbh01.ds.corp.yahoo.com [207.126.227.249]) by mrout1-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id n9KHXcw2046264 for ; Tue, 20 Oct 2009 10:33:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:user-agent:date:subject:from:to:message-id: thread-topic:thread-index:in-reply-to:mime-version:content-type: content-transfer-encoding:return-path:x-originalarrivaltime; b=LfdR7ocvFhPHTLyd223KEih3CupHBpRNCApsfYqZdVthoAEYxY3LvHlW6rpAC62J Received: from SNV-EXVS09.ds.corp.yahoo.com ([207.126.227.86]) by SNV-EXBH01.ds.corp.yahoo.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 20 Oct 2009 10:33:38 -0700 Received: from 10.73.146.106 ([10.73.146.106]) by SNV-EXVS09.ds.corp.yahoo.com ([207.126.227.84]) via Exchange Front-End Server snv-webmail.corp.yahoo.com ([207.126.227.60]) with Microsoft Exchange Server HTTP-DAV ; Tue, 20 Oct 2009 17:33:37 +0000 User-Agent: Microsoft-Entourage/12.20.0.090605 Date: Tue, 20 Oct 2009 10:33:37 -0700 Subject: Re: Cluster Configuration Issues From: Mahadev Konar To: Message-ID: Thread-Topic: Cluster Configuration Issues Thread-Index: AcpRqHyzEJsGLc1dTZmEmwrLUe3TQgAAvfWz In-Reply-To: <5D66A842901F8E41815AF6D27A28EC490A84A3FAC4@Mail-Ab02.rmg-ny.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 20 Oct 2009 17:33:38.0127 (UTC) FILETIME=[7536E5F0:01CA51AB] X-Virus-Checked: Checked by ClamAV on apache.org HI Mark, ZooKeeper does not create the myid file in the data directory. Looking at the config file it looks like it is missing the quorum configuration for other servers. Please take alook at http://hadoop.apache.org/zookeeper/docs/r3.2.1/zookeeperAdmin.html#sc_zkMuli tServerSetup You will need to add config options for other servers in the quorum in the config file. Thanks mahadev On 10/20/09 10:12 AM, "Mark Vigeant" wrote: > Hey- > > So I'm trying to run hbase on 4 nodes, and in order to do that I need to run > zookeeper in replicated mode (I could have hbase run the quorum for me, but > it's suggested that I don't). > > I have an issue though. For some reason the id I'm assigning each server in > the file "myid" in the assigned data directory is not getting read. I feel > like another id is being created and put somewhere else. Does anyone have any > tips on starting a zookeeper quorum? Do I create the myid file myself or do I > edit one once it is created by zookeeper? > > This is what my config looks like: > ticktime=2000 > dataDir=/home/hadoop/zookeeper > clientPort=2181 > initLimit=5 > syncLimit=2 > server.1=hadoop1:2888:3888 > > The name of my machine is hadoop1, with user name hadoop. In > /home/hadoop/zookeeper I've created a myid file with the number 1 in it. > > Mark Vigeant > RiskMetrics Group, Inc. >