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 873C010DB8 for ; Wed, 22 Jan 2014 21:04:21 +0000 (UTC) Received: (qmail 76291 invoked by uid 500); 22 Jan 2014 21:04:18 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 76174 invoked by uid 500); 22 Jan 2014 21:04:18 -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 76166 invoked by uid 99); 22 Jan 2014 21:04:18 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jan 2014 21:04:18 +0000 Received: from localhost (HELO mail-wg0-f43.google.com) (127.0.0.1) (smtp-auth username enis, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jan 2014 21:04:17 +0000 Received: by mail-wg0-f43.google.com with SMTP id y10so833359wgg.22 for ; Wed, 22 Jan 2014 13:04:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=j+7S4ydVMVtq/n32ysRK1YJi1s36l1o0sktMb+W6IEg=; b=U22HkT7jrQdogvrzkIaDi3o5XG9DkXlUeUBEO/1ENcmKPffnaPvlaNtq5xXcIArlys vIJh3LV1Q+gZjouxOFHFnPVX99xfze95TMa0O3x384Ef4Q0Xhn/umxndTzofMnl/7MbA s0GTPfHSA3bJplYig07myukwi5XpORtWucg7tyqC3xqRcmV7BcQCrJr1wdO7cgvqp/Qn ukS8RIeN9e9gytqEGPYyczCiaSDsJdARXx6M9+Y1CW9rzij4x8hh+uVKIkbzVPMZv35A /ZUBD9+SjMqz5YIUxg5Oqfe4BqJCcG2MlFfj0eovsP8BUXvqVsGtkjBJuP8od9PjhHum r8xQ== X-Received: by 10.194.24.65 with SMTP id s1mr3760741wjf.38.1390424656220; Wed, 22 Jan 2014 13:04:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.59.228 with HTTP; Wed, 22 Jan 2014 13:03:56 -0800 (PST) In-Reply-To: <1390378958126-4055099.post@n3.nabble.com> References: <1390321086341-4055067.post@n3.nabble.com> <1390378958126-4055099.post@n3.nabble.com> From: =?UTF-8?Q?Enis_S=C3=B6ztutar?= Date: Wed, 22 Jan 2014 13:03:56 -0800 Message-ID: Subject: Re: Hbase Installation on top of HDFS high availability To: hbase-user Content-Type: multipart/alternative; boundary=047d7b472142b89b6304f095775d --047d7b472142b89b6304f095775d Content-Type: text/plain; charset=UTF-8 You can find the manual for HDP here: http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.0.5.0/bk_system-admin-guide/content/ch_hadoop-ha.html I think you have to configure your hbase root dir and client side hdfs configuration. Enis On Wed, Jan 22, 2014 at 12:22 AM, jaksky wrote: > I am using HBase 0.96.0 as I am running a Hortonworks HDP 2.0. The issue is > that when my NameNode does perform the fail over the HBase gets completely > stacked. I think that the problem is that HBase is still pointing to the > previous namennode but couldn't find a manual how to set it up correctly. > > > > -- > View this message in context: > http://apache-hbase.679495.n3.nabble.com/Hbase-Installation-on-top-of-HDFS-high-availability-tp4055067p4055099.html > Sent from the HBase User mailing list archive at Nabble.com. > --047d7b472142b89b6304f095775d--