Sorry for sending this email again , because our mail sever had some
problem this morning!

Yes.. If HBase master fails, it loses its handle in ZK. The backup master
will register itself as the new master and all works thereafter.

Is there any document for that setup?
Thanks you


Fleming Chiu(邱宏明)
707-2260
[email protected]
週一無肉日吃素救地球(Meat Free Monday Taiwan)




                                                                                
                                                                      
                      Amandeep Khurana                                          
                                                                      
                      <[email protected]        To:      [email protected]   
                                                                      
                      >                        cc:      (bcc: Y_823910/TSMC)    
                                                                      
                                               Subject: Re: Hbase production 
deployment                                                               
                      2010/05/26 12:05                                          
                                                                      
                      PM                                                        
                                                                      
                      Please respond to                                         
                                                                      
                      user                                                      
                                                                      
                                                                                
                                                                      
                                                                                
                                                                      




Yes.. If HBase master fails, it loses its handle in ZK. The backup master
will register itself as the new master and all works thereafter.


Amandeep Khurana
Computer Science Graduate Student
University of California, Santa Cruz


2010/5/25 <[email protected]>

> Thank for your reply.
> You mean we should have a backup server with the same configure of
running
> hbase master.
> I am curious about how zookeeper can prevent from SPOF, it's protecting
> hbase master fail, right?
>
>
> Fleming Chiu(邱宏明)
> 707-2260
> [email protected]
> 週一無肉日吃素救地球(Meat Free Monday Taiwan)
>
>
>
>
>
>                       Amandeep Khurana
>                      <[email protected]        To:
> [email protected]
>                      >                        cc:      (bcc:
Y_823910/TSMC)
>                                               Subject: Re: Hbase
production
> deployment
>                      2010/05/26 11:22
>                      AM
>                      Please respond to
>                      user
>
>
>
>
>
>
> Thats a good setup. You probably dont need a dedicated box for secondary
> namenode and could consider having another node as a backup HBase
master...
>
> 2010/5/25 <[email protected]>
>
> >
> > Hi there,
> > According to the previous email about HBase: minimal number of boxes.
> > I would like to know how to deploy it for each component,
> > if there are 60 machines for our production cluster.
> > Trying to show my deployment plan, and want to get your suggestions.
> > Thank you.
> >
> > Our machine spec : CPU     : R410 1U/4Core
> >                   Memory  : 12G
> >                   HD      : 2*300GB
> >
> > Zookeeper                *  3    (dedicated)
> > Hadoop/Hbase Master      *  1    (dedicated)
> > Secondary NameNode       *  1    (dedicated)
> > DataNode & Region Server * 55
> >
> >
> >
> >
> > Fleming Chiu(邱宏明)
> > 707-2260
> > [email protected]
> > 週一無肉日吃素救地球(Meat Free Monday Taiwan)
> >
> >
> >
> >
> >
>
---------------------------------------------------------------------------
> >                                                         TSMC PROPERTY
> >  This email communication (and any attachments) is proprietary
> information
> >  for the sole use of its
> >  intended recipient. Any unauthorized review, use or distribution by
> anyone
> >  other than the intended
> >  recipient is strictly prohibited.  If you are not the intended
> recipient,
> >  please notify the sender by
> >  replying to this email, and then delete this email and any copies of
it
> >  immediately. Thank you.
> >
> >
>
---------------------------------------------------------------------------
> >
> >
> >
> >
>
>
>
>
>
>
---------------------------------------------------------------------------
>                                                          TSMC PROPERTY
>  This email communication (and any attachments) is proprietary
information
>  for the sole use of its
>  intended recipient. Any unauthorized review, use or distribution by
anyone
>  other than the intended
>  recipient is strictly prohibited.  If you are not the intended
recipient,
>  please notify the sender by
>  replying to this email, and then delete this email and any copies of it
>  immediately. Thank you.
>
>
---------------------------------------------------------------------------
>
>
>
>




 --------------------------------------------------------------------------- 
                                                         TSMC PROPERTY       
 This email communication (and any attachments) is proprietary information   
 for the sole use of its                                                     
 intended recipient. Any unauthorized review, use or distribution by anyone  
 other than the intended                                                     
 recipient is strictly prohibited.  If you are not the intended recipient,   
 please notify the sender by                                                 
 replying to this email, and then delete this email and any copies of it     
 immediately. Thank you.                                                     
 --------------------------------------------------------------------------- 



Reply via email to