Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> HBase is not running.


Copy link to this message
-
Re: HBase is not running.
I can.  I'll change /etc/sysconfig/network to localhost, for a hostname.

In CentOS/Fedora/Red Hat, /etc/hostname does not exist and it's
/etc/sysconfig/network :) .
On Fri, May 24, 2013 at 4:25 PM, Jay Vyas <[EMAIL PROTECTED]> wrote:

> +1 for a VM on your own machine.  That's how I do it because its easy to
> control and muck with network settings .
>
> Cant you just Edit etc/hostname file ?
>
> On May 24, 2013, at 4:03 PM, Jean-Daniel Cryans <[EMAIL PROTECTED]>
> wrote:
>
> > This is a machine identity problem. HBase simply uses the normal Java
> > APIs and asks "who am I?". The answer it gets is
> > ip72-215-225-9.at.at.cox.net. Changing this should only be a matter of
> > DNS configs, starting with /etc/hosts. What is your machine's hostname
> > exactly (run "hostname")? When you ping it, what does it return? That
> > should get you started. Does you machine even have a local IP when you
> > run ifconfig? If not, all you can do is force everything to localhost
> > in your network configs. It also means you cannot use HBase in a
> > distributed fashion.
> >
> > Changing the code seems like a waste of time, HBase is inherently
> > distributed and it relies on machines having their network correctly
> > configured. Your time might be better spent using a VM on your own
> > machine.
> >
> > J-D
> >
> > On Fri, May 24, 2013 at 12:38 PM, Yves S. Garret
> > <[EMAIL PROTECTED]> wrote:
> >> That seems to be the case.  The thing that I don't get is if I missed
> any
> >> "global" setting in order to make everything turn towards localhost.
>  What
> >> am I missing?
> >>
> >> I'll scour the HBase docs again.
> >>
> >>
> >> On Fri, May 24, 2013 at 1:17 PM, Jay Vyas <[EMAIL PROTECTED]> wrote:
> >>
> >>> Yes ... get hostname and /etc/hosts synced up properly and i bet that
> will
> >>> fix it
> >>>
> >>>
> >>> On Fri, May 24, 2013 at 12:41 PM, Jean-Daniel Cryans <
> [EMAIL PROTECTED]
> >>>> wrote:
> >>>
> >>>> Ah yeah the master advertised itself as:
> >>>>
> >>>> Attempting connect to Master server at
> >>>> ip72-215-225-9.at.at.cox.net,46122,1369408257140
> >>>>
> >>>> So the region server cannot find it since that's the public address
> >>>> and nothing's reachable through that. Now you really need to fix your
> >>>> networking :)
> >>>>
> >>>> J-D
> >>>>
> >>>> On Fri, May 24, 2013 at 8:21 AM, Yves S. Garret
> >>>> <[EMAIL PROTECTED]> wrote:
> >>>>> Ok, weird, it still seems to be looking towards Cox.
> >>>>>
> >>>>> Here is my hbase-site.xml file:
> >>>>> http://bin.cakephp.org/view/628322266
> >>>>>
> >>>>>
> >>>>> On Thu, May 23, 2013 at 7:35 PM, Jean-Daniel Cryans <
> >>> [EMAIL PROTECTED]
> >>>>> wrote:
> >>>>>
> >>>>>> No, I meant hbase.master.ipc.address and
> >>>>>> hbase.regionserver.ipc.address. See
> >>>>>> https://issues.apache.org/jira/browse/HBASE-8148.
> >>>>>>
> >>>>>> J-D
> >>>>>>
> >>>>>> On Thu, May 23, 2013 at 4:34 PM, Yves S. Garret
> >>>>>> <[EMAIL PROTECTED]> wrote:
> >>>>>>> Do you mean hbase.master.info.bindAddress and
> >>>>>>> hbase.regionserver.info.bindAddress?  I couldn't find
> >>>>>>> anything else in the docs.  But having said that, both
> >>>>>>> are set to 0.0.0.0 by default.
> >>>>>>>
> >>>>>>> Also, I checked out 127.0.0.1:60010 and 0.0.0.0:60010,
> >>>>>>> no web gui.
> >>>>>>>
> >>>>>>>
> >>>>>>> On Thu, May 23, 2013 at 7:19 PM, Jean-Daniel Cryans <
> >>>> [EMAIL PROTECTED]
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> It should only be a matter of network configuration and not a
> >>> matter
> >>>>>>>> of whether you are a Hadoop expert or not. HBase is just trying to
> >>>> get
> >>>>>>>> the machine's hostname and bind to it and in your case it's given
> >>>>>>>> something it cannot use. It's unfortunate.
> >>>>>>>>
> >>>>>>>> IIUC your machine is hosted on cox.net? And it seems that while
> >>>>>>>> providing that machine they at some point set it up so that its
> >>>>>>>> hostname would resolve to a public address. Sounds like a
> >>>>>>>> misconfiguration. Anyways, you can edit your /etc/hosts so that