Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 39745 invoked from network); 15 Jun 2009 17:00:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Jun 2009 17:00:32 -0000 Received: (qmail 52303 invoked by uid 500); 15 Jun 2009 17:00:43 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 52269 invoked by uid 500); 15 Jun 2009 17:00:43 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 52259 invoked by uid 99); 15 Jun 2009 17:00:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jun 2009 17:00:43 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of fredrik.mollerstrand@gmail.com designates 72.14.220.152 as permitted sender) Received: from [72.14.220.152] (HELO fg-out-1718.google.com) (72.14.220.152) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jun 2009 17:00:33 +0000 Received: by fg-out-1718.google.com with SMTP id 22so1131826fge.12 for ; Mon, 15 Jun 2009 10:00:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=p2rSAoTv4mTmr6vJ1r8lli+JYHhh8roKOFUkCJ1LF00=; b=qjkhTUh3KtBglAP+q0satYo2J2TMHO3vJZrEaF/QNXaKTM59+n/1Ag08lWvW20ROWi Kk0IAR3IqUrleh2bBA7hR4mq+fYwcKp5TvmOm+s6fwJCE/A1ljjncrQSSmsLb1txKfrH 8JiKt/NnTsgZ1VNrO4sD6tS33DchxxJe9OxGQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=E11tvhvs/q44fgXIV3iyMOWla0vSf2NQ7RPG2w31yu5+/MOJNyWbWHD5rRR85RD/Ml CskKkj2M32O8M/z5gyg59D08wSnDVxj0Gp4aMeIAFpAmupWeb6fZC6pEJNXe+LSacW/t Hbwcv5e1PfnaD3dL8shGGmDqE3GOo0SiXDNUA= MIME-Version: 1.0 Sender: fredrik.mollerstrand@gmail.com Received: by 10.86.68.1 with SMTP id q1mr6824840fga.10.1245085207911; Mon, 15 Jun 2009 10:00:07 -0700 (PDT) Date: Mon, 15 Jun 2009 18:00:07 +0100 X-Google-Sender-Auth: 731b8d6437b82060 Message-ID: Subject: HMaster and /etc/hosts From: =?UTF-8?Q?Fredrik_M=C3=B6llerstrand?= To: hbase-user@hadoop.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello list! I've spent the better part of the afternoon upgrading from 0.19.3 to trunk, and I did fall into a hole or two. Specifically, it turns out that we rely on DNS lookups to find out what address HMaster binds to, which caused me some grief. The documentation is also weak on what part Zookeeper plays in the process; a stronger write-up of how HBase utilizes Zookeeper would be a great help in troubleshooting issues like this. Basically, I saw the region servers trying to connect to 127.0.0.1:6000 without any hint as to why, neither in the (default) configuration nor the logs. HMaster happily reported this: INFO org.apache.hadoop.hbase.master.HMaster: My address is master2.internal.net:6000 quickly followed by: INFO org.apache.hadoop.hbase.master.HMaster: HMaster initialized on 127.0.0.1:6000 The cause was simple and my face-palm genuine as the realization struck me: there was a record for master2 in the hosts file, and it was pointing to 127.0.0.1. I suggest that an hbase.master.address option (that overrides any resolved address) would make it easier to get the installation up and running. Cheers, Fredrik