Return-Path: 
 <user-return-24655-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
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 66F1CB503
	for <apmail-hbase-user-archive@www.apache.org>;
 Thu, 12 Jan 2012 21:57:00 +0000 (UTC)
Received: (qmail 77504 invoked by uid 500); 12 Jan 2012 21:56:58 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 77352 invoked by uid 500); 12 Jan 2012 21:56:58 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 77339 invoked by uid 99); 12 Jan 2012 21:56:57 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jan 2012 21:56:57 +0000
X-ASF-Spam-Status: No, hits=-0.5 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of opus111@gmail.com designates
 209.85.216.169 as permitted sender)
Received: from [209.85.216.169] (HELO mail-qy0-f169.google.com)
 (209.85.216.169)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jan 2012 21:56:48 +0000
Received: by qcsd17 with SMTP id d17so1593233qcs.14
        for <user@hbase.apache.org>; Thu, 12 Jan 2012 13:56:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        bh=1mnh/7KBfS5XzfV0MKqnd8h1Q/rBgA7cypZi39zx8hk=;
        b=XcDxm6sBA7m17OTuWS9S6QzyrM3vksvOkqDnqjvXXY3MLyXm9nwBWgthklOClYzeaH
         YeXs1tXSKPsiQcGqoZtsK96lDwoos3Z2E9/amuu5SrN+xx0PPm8g/dVvqG7Zo1oO+5hz
         lad62LmfKD/9N2Goxf2ZAKHxu5heBfIcpGQ58=
Received: by 10.229.135.11 with SMTP id l11mr2140033qct.140.1326405387171;
        Thu, 12 Jan 2012 13:56:27 -0800 (PST)
Received: from Hemiola.local (static-71-174-62-39.bstnma.fios.verizon.net.
 [71.174.62.39])
        by mx.google.com with ESMTPS id fe5sm12382285qab.5.2012.01.12.13.56.25
        (version=SSLv3 cipher=OTHER);
        Thu, 12 Jan 2012 13:56:26 -0800 (PST)
Message-ID: <4F0F5708.4080906@gmail.com>
Date: Thu, 12 Jan 2012 16:56:24 -0500
From: Peter Wolf <opus111@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: user@hbase.apache.org
CC: Jean-Daniel Cryans <jdcryans@apache.org>
Subject: Re: EC2 remote client woes
References: <4F0F0831.6090403@gmail.com>
 <CANYdkkNeNmxwFkiwTbPF28GiNdAaSv3ZLpqm4CwXRn9P5F36bw@mail.gmail.com>
 <4F0F17CD.6050803@gmail.com>
 <CAGpTDNfVCewRDhTEdJ4vozXy7CzYw7NKh04TDRdPPDErG0pEJw@mail.gmail.com>
 <4F0F466E.5020903@gmail.com>
 <CAGpTDNfbo2mrV+cOgYV5d4qGM8zv9Gz-ELd3f7Ku3R2cAdXnrA@mail.gmail.com>
In-Reply-To: 
 <CAGpTDNfbo2mrV+cOgYV5d4qGM8zv9Gz-ELd3f7Ku3R2cAdXnrA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Sorry, that's a typo in my email.  Here is my config file again (that 
doesn't work)

<configuration>
<property>
<name>hbase.zookeeper.quorum</name>
<value>ip-AA-BBB-C-DDD.ec2.internal</value>
<description>Standalone Server</description>
</property>
</configuration>

I double checked, and I am using ip-AA-BBB-C-DDD.ec2.internal 
consistently in config files and code.

P




On 1/12/12 4:24 PM, Jean-Daniel Cryans wrote:
> Yes, it's the same thing, which is why I think the additional
> ec2.internal in your hbase-site is suspicious. Let me reiterate:
>
> This works:
>
> echo stat|nc ip-XX-YYY-Z-QQQ.ec2.internal 2181
>
> But this config doesn't:
>
> <value>ip-XX-YYY-Z-QQQ.ec2.internal.ec2.internal</value>
>
> Now what happens if you just use the same one, the one that works?
>
> J-D
>
> On Thu, Jan 12, 2012 at 12:45 PM, Peter Wolf<opus111@gmail.com>  wrote:
>> I'm a N00B, so I'm not sure of anything... but it is working now using the
>> Java Client API, and XXX.ec2.internal address on both server and client.
>>
>> The problem seems to be 'hbase shell', which is odd as I would have thought
>> it sat on top of the Java API.
>>
>> P
>>
>>
>>
>>
>> On 1/12/12 1:22 PM, Jean-Daniel Cryans wrote:
>>> Your config file on the remote machine has:
>>>
>>> ip-XX-YYY-Z-QQQ.ec2.internal.ec2.internal
>>>
>>> You sure about the extra ec2.internal?
>>>
>>> J-D
>>>
>>> On Thu, Jan 12, 2012 at 9:26 AM, Peter Wolf<opus111@gmail.com>    wrote:
>>>> Oh yeah!  The code did it :-D
>>>>
>>>> For those that come after, I guess 'hbase shell' is broken for remote
>>>> access.  Use the raw Java API
>>>>
>>>> Many thanks again Mark!
>>>>
>>>>
>>>>
>>>>
>>>> On 1/12/12 11:40 AM, Mark Kerzner wrote:
>>>>> 1. Look in the logs;
>>>>> 2. I think hbase shell works only locally;
>>>>> 3. The code below worked for me, and I don't use a config file, but give
>>>>> the params directly:
>>>>>
>>>>>      public void connect() throws IOException {
>>>>>          Configuration hConf = HBaseConfiguration.create();
>>>>>          hConf.set(MyConstants.HBASE_CONFIGURATION_ZOOKEEPER_QUORUM,
>>>>> MyConstants.zookeeperUrl);
>>>>>          hConf.set(MyConstants..HBASE_CONFIGURATION_ZOOKEEPER_CLIENTPORT,
>>>>> MyConstants.zookeeperPort);
>>>>>          String tableName = "MyTable";
>>>>>          HTable hTable = new HTable(hConf, tableName);
>>>>>          hTable.close();
>>>>>      }
>>>>>
>>>>> Mark
>>>>>
>>>>> On Thu, Jan 12, 2012 at 10:20 AM, Peter Wolf<opus111@gmail.com>
>>>>>   wrote:
>>>>>
>>>>>> Still no love...  Any suggestions?
>>>>>>
>>>>>> I'm on EC2, and I am trying to set up a Pseudo-Distributed HBaser
>>>>>> Server
>>>>>> on one machine, and access it from another.  Both machines are EC2.
>>>>>>
>>>>>> I have already found the doc below, and I followed the instructions
>>>>>>
>>>>>>
>>>>>>
>>>>>> http://hbase.apache.org/book.**html#client_dependencies<http://hbase.apache.org/book.html#client_dependencies>
>>>>>>
>>>>>>
>>>>>> My server is up and running, and I can access it from an 'hbase shell'
>>>>>> on
>>>>>> the machine.  The hbase-site.xml is ...
>>>>>>
>>>>>>    <configuration>
>>>>>>    <property>
>>>>>>    <name>hbase.zookeeper.quorum</**name>
>>>>>>    <value>ip-XX-YYY-Z-QQQ.ec2.**internal</value>
>>>>>>    </property>
>>>>>>    <property>
>>>>>>    <name>hbase.cluster.**distributed</name>
>>>>>>    <value>true</value>
>>>>>>    </property>
>>>>>>    <property>
>>>>>>    <name>hbase.rootdir</name>
>>>>>>    <value>hdfs://localhost/hbase<**/value>
>>>>>>    </property>
>>>>>>    </configuration>
>>>>>>
>>>>>> The client machine hbase-site.xml is...
>>>>>>
>>>>>>    <configuration>
>>>>>>    <property>
>>>>>>    <name>hbase.zookeeper.quorum</**name>
>>>>>>    <value>ip-XX-YYY-Z-QQQ.ec2.**internal.ec2.internal</value>
>>>>>>    <description>Pseudo Distributed Server</description>
>>>>>>    </property>
>>>>>>    </configuration>
>>>>>>
>>>>>> And when I try 'hbase shell' remotely, I get this...
>>>>>>
>>>>>>    hbase(main):001:0>      status 'detailed'
>>>>>>
>>>>>>    ERROR: org.apache.hadoop.hbase.**ZooKeeperConnectionException: HBase
>>>>>>    is able to connect to ZooKeeper but the connection closes
>>>>>>    immediately. This could be a sign that the server has too many
>>>>>>    connections (30 is the default). Consider inspecting your ZK server
>>>>>>    logs for that error and then make sure you are reusing
>>>>>>    HBaseConfiguration as often as you can. See HTable's javadoc for
>>>>>>    more information.
>>>>>>
>>>>>>
>>>>>>
>>>>>>