Happy that you could figure out quickly and even happier that your
wrote back to the list with details.
Thanks!
J-D
On Thu, Apr 28, 2011 at 3:24 AM, Alex Romanovsky
wrote:
> Thank you a lot for your help Jean!
>
> It was a reverse DNS lookup issue - we recently changed our default
> domain suff
Thank you a lot for your help Jean!
It was a reverse DNS lookup issue - we recently changed our default
domain suffix.
I noticed that by looking up the server name from the "No HServerInfo
found" message through the list returned by
admin.getClusterStatus().getServerInfo().
I'll drop the DNS cach
Hi Alex,
Before answering I made sure it was working for me and it does. In
your master log after killing the -ROOT- region server you should see
lines like this:
INFO org.apache.hadoop.hbase.zookeeper.RegionServerTracker:
RegionServer ephemeral node deleted, processing expiration
[servername]
DE
Hi,
I am trying failover cases on a small 3-node fully-distributed cluster
of the following topology:
- master node - NameNode, JobTracker, QuorumPeerMain, HMaster;
- slave nodes - DataNode, TaskTracker, QuorumPeerMain, HRegionServer.
ROOT and META are initially served by two different nodes.
I
Hi,
I am trying failover cases on a small 3-node fully-distributed cluster
of the following topology:
- master node - NameNode, JobTracker, QuorumPeerMain, HMaster;
- slave nodes - DataNode, TaskTracker, QuorumPeerMain, HRegionServer.
ROOT and META are initially served by two different nodes.
I
