Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 731FCFBD8 for ; Thu, 25 Apr 2013 12:45:18 +0000 (UTC) Received: (qmail 44210 invoked by uid 500); 25 Apr 2013 12:45:02 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 43927 invoked by uid 500); 25 Apr 2013 12:44:59 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 43832 invoked by uid 99); 25 Apr 2013 12:44:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Apr 2013 12:44:55 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [209.85.212.49] (HELO mail-vb0-f49.google.com) (209.85.212.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Apr 2013 12:44:51 +0000 Received: by mail-vb0-f49.google.com with SMTP id 11so2623390vbf.36 for ; Thu, 25 Apr 2013 05:44:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=XwqS9BAbjSD7jhesBuPe1RFZLx8Kc3QENmDEoZivzCk=; b=ZqOZkgeXs9X+cM/p9CQ4l/L25xSi7KJzs0a8bZF/6GjC1LJ/x8LU7voEJHOUr5EZuZ gXIgvEu4vAh0yP263jOOmdqxdCEjVvkNtCCg42jq6R7XvZT6NA5+1ynt19PARKpQZJGY +UiabWWlIi1PRtLhORkm/tKxIs9f5sbXwiSV9P8OSPoew/Pnd+xTCXYPUE1601M1AFIA SPaSZTeNYCIaOkxFAI/w4I8eSnTHljZLPLU/+NDyjXcIv+qrZ539a10Yfex94o3wuFIP D1qns16qh66orLlDF9sV74dB43/bVNVjvx7ZCcHvErEC9P2nV+1EvWzfdhB7L5n7LLZD 6NHg== X-Received: by 10.58.75.46 with SMTP id z14mr26700012vev.52.1366893850186; Thu, 25 Apr 2013 05:44:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.94.8 with HTTP; Thu, 25 Apr 2013 05:43:50 -0700 (PDT) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Thu, 25 Apr 2013 08:43:50 -0400 Message-ID: Subject: Re: Re: While starting 3-nodes cluster hbase: WARN org.apache.zookeeper.ClientCnxn: Session 0x0 for server null To: user@hbase.apache.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmQCPPJuXrU0FBVC8Pn5d+pmfuDD/k7Tg7AON0a/MySI76MYGntZXos/u9Kz6MkZJK2OFIQ X-Virus-Checked: Checked by ClamAV on apache.org Hi John, bin/start-dfs is to start hadoop, right? Why are you trying to start that from HBase Master? You said that you hadoop is already configured and working fine. You should start HBase with bin/start-hbase.sh which will start the master and the regionservers. Also, in your host file, please replace "127.0.0.1 debian01" by the real IP. It will help. Keep us posted. JM 2013/4/24 John Foxinhead : > I tried this way: I started hadoop, and it's all ok, so go on. > I setted HBASE_MANAGES_ZK=false, so i could start zookeeper, try it and > check the problem. > I changed the zookeeper.quorum to jobtracker,datanode1 instead of > zookeeper1,zookeeper2 because the IP are the same, but in log file the > hostname reported was jobtracker and datanode1, while in zookeeper.quorum i > setted zookeper1,zookeeper2 so i changed this property because in hbase > documentation it's recommended to set the same hostname specified in log > file otherwise zookeeper nodes could not recognise themselves as zookeeper > nodes and maybe master could have problem logging. Anyway, I made this > change in all the nodes. > I start zookeeper in zookeeper nodes, and it works now because when i log > with bin/hbase zkcli from master node (who is not running zookeeper) It > logs at datanode1:2181 (where zookeeper is running) and commands like "ls > /" work. > When i use from master /bin/start-dfs the only output is "starting > master...". When I see log file i noticed that master send a zookeeper > request to 0.0.0.0:2181 and accept response from 127.0.0.2181, while using > bin/hbase zkcli it connect with datanode1.2181. This is very strange, I > think. What could be the reason why?