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 AA1A010BF1 for ; Mon, 9 Dec 2013 04:01:18 +0000 (UTC) Received: (qmail 36500 invoked by uid 500); 9 Dec 2013 04:00:47 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 36421 invoked by uid 500); 9 Dec 2013 04:00:39 -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 36333 invoked by uid 99); 9 Dec 2013 04:00:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Dec 2013 04:00:27 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ruralhunter@gmail.com designates 209.85.160.43 as permitted sender) Received: from [209.85.160.43] (HELO mail-pb0-f43.google.com) (209.85.160.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Dec 2013 04:00:21 +0000 Received: by mail-pb0-f43.google.com with SMTP id rq2so4577772pbb.30 for ; Sun, 08 Dec 2013 20:00:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=4n2P4Yojr5krYswEd2LfnU13UuLQgfq09jWNjL3x5yw=; b=cN0rdVrOSFBjuFeiBnXB3PLCBsOvgc40qKvxtvioHeaqFnzMUSLTVan674XYo/kJWU rN51yaGsKJqWpRBtDBNVOAx3QFbDjqBK+2QNPl2JyTwI3jmvdN6tTcFYPomvVONV5D2O Jc+VnBNuEEJfaNeUq/Qy4cRNa3arD3B07XMDSSkz3ytKYDebt5GQagrz0gKHCCQONi6c uv42Yg8udALg1i6R7VfjcYh5xc2Z9BZY62wthHknuKLdjpdwj/CC4Vka6F7XrZQQlv/o Yl5zHqSlJ7IiKsFC52hcVAe5PM6FirsAXwx8Zihq9EACGyRPYZhCSO5jhHovgcVGcQ61 8D9g== X-Received: by 10.66.7.68 with SMTP id h4mr18542186paa.0.1386561599918; Sun, 08 Dec 2013 19:59:59 -0800 (PST) Received: from [192.168.2.102] ([116.226.61.30]) by mx.google.com with ESMTPSA id by1sm13986030pbd.25.2013.12.08.19.59.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Dec 2013 19:59:59 -0800 (PST) Message-ID: <52A54038.40405@gmail.com> Date: Mon, 09 Dec 2013 11:59:52 +0800 From: Rural Hunter User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: user@hbase.apache.org Subject: Re: Remote java client hang References: <1386346511.5806.ezmlm@hbase.apache.org> <52A1FADD.8010302@gmail.com> <52A3C560.2000801@gmail.com> In-Reply-To: <52A3C560.2000801@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org I tested the test app in LAN and it worked. Is it possible for the client to access hbase cluster in WAN? 于 2013/12/8 9:03, Rural Hunter 写道: > No, I didn't. What's that for? I just followed this guide: > http://archive.cloudera.com/cdh/3/hbase/client_dependencies.html > Meanwhile, I have another question. My hbase cluster is running in a > inner-network. All master and slaves hostnames are resolved to LAN ip > like this: > master 192.168.1.2 > slave1 192.168.1.3 > slave2 192.168.1.4 > ... > > So in this case, although all the servers have WAN ips, is it possible > for the client in WAN to access hbase cluster? Does zookeeper return > LAN hostnames to the client? I'm worrying about this also because I > found some hbase ports are listening on LAN port only like this: > tcp6 0 0 192.168.1.8:60020 :::* LISTEN > > while zookeeper is listening on all network interfaces: > tcp6 0 0 :::2181 :::* LISTEN > > 于 2013/12/7 15:55, Ted Yu 写道: >> Did you specify hbase.rootdir ? >> >> Cheers >> >> >> On Sat, Dec 7, 2013 at 12:27 AM, Rural Hunter >> wrote: >> >