The impact of master going down is that during the period when cluster runs without master, certain operations can't be performed (for example, admin operations like creating or modifying tables, or internal cluster workflows like distributed log splitting to handle crashed region servers or region assignment).
-Mikhail 2014-07-03 0:45 GMT-07:00 Mikhail Antonov <[email protected]>: > Hi Yanglin, > > what exactly do you mean by "system..need to take any failover" - any > manual action by cluster admin? Failover happens automatically based on > zookeeper timeout for current active master. Currently, hbase cluster has 1 > active master and several backup masters. When backup masters notice active > master going down, they elect new one, and the new one takes over > responsibilities. > > -Mikhail > > > 2014-07-03 0:40 GMT-07:00 yl wu <[email protected]>: > > Hi All, >> >> I've read many articles, including Bertozzi's Who needs a Master, but I am >> still confused about the Hmaster. >> >> If the Hmaster goes down, does the system need to take any failover ? >> Or just elect a new master, and the new one can restore all the >> information >> from hbase:meta? >> >> Best regards, >> Yanglin >> > > > > -- > Thanks, > Michael Antonov > -- Thanks, Michael Antonov
