hbase
  • Introduction
  • Concepts
  • Hbase Architecture
    • Region servers
      • Regions
      • HFile
      • WAL(HLog)
      • How the Components Work Together
      • BlockCache
      • Region Split
      • Store(HStore OR Memstore))
      • HBase Region Flush
    • Special Tables ROOT , META
    • Fault Tolerance( Failover)
    • Data Locality
    • ZooKeeper: The Coordinator
    • HBase HMaster
    • Read Load Balancing
    • HBase Minor Compaction
    • HBase Major Compaction
    • HBase Read Merge
  • Queries
  • HBase Shell
    • Guide Lines
    • overview-example
  • HBase Read
  • HBase Write
  • Known Use Cases
  • HBase Data Model
  • References
  • Hands on
  • Case Studies
  • Notes
Powered by GitBook
On this page

Was this helpful?

  1. Hbase Architecture

ZooKeeper: The Coordinator

PreviousData LocalityNextHBase HMaster

Last updated 5 years ago

Was this helpful?

HBase uses ZooKeeper as a distributed coordination service to maintain server state in the cluster.

Zookeeper maintains which servers are alive and available, and provides server failure notification.

Zookeeper uses consensus to guarantee common shared state. Note that there should be three or five machines for consensus.