Thanks for the suggestions.

I restarted the cluster again.  Now things are fine.

I think the mistake I might have done earlier is that I did not restart HDFS 
nodes (name node + datanodes), but just the HBase nodes (master, zookeeper and 
region servers).
Now, I restarted all, after cleaning the zookeeper data.

Regards,
Srikanth

-----Original Message-----
From: shashwat shriparv [mailto:dwivedishash...@gmail.com] 
Sent: Wednesday, May 02, 2012 6:40 PM
To: user@hbase.apache.org
Subject: Re: Master startup - Taking forever to complete - "Assigning META 
Region"

Check if IP has changed.

On Wed, May 2, 2012 at 6:28 PM, Ramkrishna.S.Vasudevan < 
ramkrishna.vasude...@huawei.com> wrote:

> May be after half an hour the Timeout monitor may try to assign it. It 
> is an internal thread that the system uses.
> But I still doubt the zookeeper data.  This problem mainly happens if 
> the zookeeper node for META is still available.
>
> Regards
> Ram
>
> > -----Original Message-----
> > From: Srikanth P. Shreenivas 
> > [mailto:srikanth_shreeni...@mindtree.com]
> > Sent: Wednesday, May 02, 2012 6:22 PM
> > To: user@hbase.apache.org
> > Subject: Master startup - Taking forever to complete - "Assigning 
> > META Region"
> >
> > We had shifted our machines from one location to another location.
> >
> > After bringing up the system,  when we started our Hadoop and HBase 
> > clusters, we realized that clocks were out of sync and region 
> > servers would not start up.
> > After syncing the clock, when we restarted the cluster, we are 
> > observing that we get error related to .META. region not being onlne.
> >
> > When we look at web console of HBase, we observed that , under the 
> > heading "Currently running tasks", we see :
> >
> > Description          Status                                        Age
> > Master startup - Assigning META region  - 341s
> >
> >
> > Any idea what could be causing this?  We tried cleaning up the 
> > zookeeper data and restarted the cluster, but the issue persists.
> >
> > We are planning to leave the server running and check back after few 
> > hours.  Not sure whether something got corrupted when clocks were 
> > out- of-sync.
> >
> >
> > Regards,
> > Srikanth
> >
> > ________________________________
> >
> > http://www.mindtree.com/email/disclaimer.html
>
>


-- 


∞
Shashwat Shriparv

Reply via email to