We don't use it at StumbleUpon (even tho I am the one who wrote most of the feature) because this feature was built having in mind that the Namenode would soon be more highly available but since it's still not and if it goes down the whole cluster goes down, then it just makes sense to put a single master with the Namenode.
A good thing tho is that a master can be killed and restarted as much as you want, thus making rolling upgrade easier. J-D On Fri, Feb 26, 2010 at 4:45 PM, Ted Yu <yuzhih...@gmail.com> wrote: > I read http://wiki.apache.org/hadoop/Hbase/MultipleMasters > If someone uses Multiple Masters in production, please share your > experience. > > Thanks > > On Tue, Feb 23, 2010 at 10:31 PM, Stack <st...@duboce.net> wrote: > >> What version are you on? There is no hbase.master in hbase 0.20.x. >> Its a vestige of 0.19 hbase. Now you specify the zookeeper ensemble >> you want to connect to. It knows who master is. >> >> Regards multi-master hbase, see >> http://wiki.apache.org/hadoop/Hbase/MultipleMasters off the main wiki >> page. >> >> St.Ack >> >> On Tue, Feb 23, 2010 at 10:06 PM, steven zhuang <zhuangxin8...@gmail.com> >> wrote: >> > hello, everyone. >> > >> > I found that we can leave hbase.master unset in hbase-site.xml, and >> > we can have a hbase cluster running OK. >> > Is there any mechanism like auto-election make one node the master? >> > >> > -- >> > best wishes. >> > steven >> > >> >
