hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ramkrishna S Vasudevan <ramakrish...@huawei.com>
Subject RE: FW: Process RIT for META and ROOT- Do we really need to wait for timeout period?
Date Tue, 16 Aug 2011 04:49:24 GMT
Hi Stack, 

What you say is when the master sees it in OPENED state.  But if the META
was in OPENING state in zk and that time the master goes down.  Now when the
master comes up again then the master will try to process the OPENING state.

        regionsInTransition.put(encodedRegionName, new RegionState( 
            regionInfo, RegionState.State.OPENING, 
            data.getStamp(), data.getOrigin()));
It will add the RIT as OPENING in master's memory and will wait for the
timeout monitor to deduct the same.

That's why I thought we need not make the META region to wait for so long in
master restart/switch scenario.  Correct me if am wrong.


-----Original Message-----
From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of Stack
Sent: Tuesday, August 16, 2011 9:56 AM
To: dev@hbase.apache.org; ramakrishnas@huawei.com
Subject: Re: FW: Process RIT for META and ROOT- Do we really need to wait
for timeout period?

On Thu, Aug 11, 2011 at 11:31 PM, Ramkrishna S Vasudevan
<ramakrishnas@huawei.com> wrote:
> Hi All,
> The scenario is while opening META region the master goes down and the
> in zookeeper is RS_OPENING for META.  Now when the master comes up it will
> process the RIT.  Here master has to wait till the timeoutmonitor deducts
> that the region has not been opened.  So if we have some default value for
> timeout then for the META region to comeup itself it may take more time.
Won't the .META. usually be moving from OPENING to OPENED?  When new
master comes up, it'll notice the changes and act accordingly?  Am I
not understanding something Ram?


View raw message