Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> HRegionserver daemon is not running on region server node


Copy link to this message
-
Re: HRegionserver daemon is not running on region server node
So - first of all:
> hbase-regionserver2: bash: line 0: cd: {HBASE_HOME}/bin/..:
> No such file or
> directory

This indicates that the environment of the process running
hbase-regionserver2 is not set correctly. It is not able to find the
directory.

Is hbase running as a different user?

I think your first step should be to get the above "No such file or
directory" errors resolved. Did you set HBASE_HOME in the  environment
manually? If a new bash env is created, will that env get inherited?

So - start simple steps first - get hbase running stand alone, then
move to pseudo / fully distributed.

By introducing variables like wired/wireless etc in your network, you
are introducing uncertainities which will bite you on an ongoing basis
(wireless going down, increased latencies, etc, etc). So - the cluster
is unlikely to be stable with such a setup.

I would recommend going with a fully wired setup, if your goal is to
have a stable hbase cluster. If it is a "at home test cluster", then
that's fine - but be prepared for frequent cluster reboots. :)

--Suraj
On Sat, Nov 26, 2011 at 11:20 PM, Vamshi Krishna <[EMAIL PROTECTED]> wrote:
> Hi suraj,
> Thank you,
>  i am using ubuntu-10.04 OS. actually i am using 3 machines out of which
> two are desktops connected with wired connection(10.0.1.54 and 10.0.1.97),
> other is laptop(10.0.1.55) connected with wireless router. i didnot modify
> any of such interface settings in hbase-site.xml file.
> Would this sort of connecting nodes (i.e using both wired and wireless
> connections) create any such problem as i mentioned? If so, atleast two
> desktop machines are connected with same wired connection, then also  it
> threw an error, like
>
> hbase-regionserver2: bash: line 0: cd: {HBASE_HOME}/bin/..: No such file or
> directory
> hbase-regionserver2: bash: {HBASE_HOME}/bin/hbase-daemon.sh: No such
> file or directory
>
> i will change hbase-site.xml as you have suggested and let you know what is
> happening. But before that answer my above query please.
>
>  One more thing is, i am running  region servers on the datanodes and
> master only, then i hope it would become co-located, right?
>
> Thank you
> On Sun, Nov 27, 2011 at 2:05 AM, Suraj Varma <[EMAIL PROTECTED]> wrote:
>
>> Vamshi:
>> What OS are you trying this on? Is it Linux / Windows?
>>
>> You can use the *.dns.interface configurations to use the specific
>> network interface that you want.
>>
>> That is, set the following configurations in your hbase-site.xml on
>> all hbase nodes
>> hbase.zookeeper.dns.interface
>> hbase.regionserver.dns.interface
>> hbase.master.dns.interface
>>
>> You can set it to lo or eth0 or eth1 per your environment.
>>
>> Restart all nodes after this and you should see them bind to the
>> specified interface.
>> You can do the same for hadoop by setting dfs.datanode.dns.interface
>> in hdfs-site.xml for hadoop nodes.
>>
>> On Windows cygwin, I've found setting that it to "localhost" works.
>>
>> Your setup should work for test environments ... for production, the
>> standard setup would be to co-locate region servers and data nodes to
>> get data locality.
>> --Suraj
>>
>> On Thu, Nov 24, 2011 at 10:51 PM, Vamshi Krishna <[EMAIL PROTECTED]>
>> wrote:
>> > Hi, i checked  by executing netstat -anp, i found
>> > tcp        0      0 127.0.1.1:60000         0.0.0.0:*
>> > LISTEN      6814/java
>> > .
>> > ***some other ports**
>> > tcp        0      0 0.0.0.0:60010           0.0.0.0:*
>> > LISTEN      6814/java .
>> > ***some other ports**
>> > .
>> > tcp        0      0 10.0.1.54:44095         10.0.1.54:9000
>> > ESTABLISHED 6814/java
>> > ***some other ports**
>> > tcp        0      0 10.0.1.54:55204         10.0.1.54:2222
>> > ESTABLISHED 6814/java
>> > ***some other ports**
>> > ***some other ports**
>> >
>> > the port of HMaster i found when i ran jps is 6814. But the same port i
>> > found in different places bound to different IPs (i.e some time
>> 127.0.1.1 ,
>> > and some times 10.0.1.54). Same is the case with all other daemons which
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB