What does hbase rely on to provide message communication mechanism?

hbase relies on "Zookeeper" to provide a message communication mechanism. ZooKeeper is a distributed, open source distributed application coordination service; as the cluster coordinator of hbase, zookeeper can coordinate and handle hbase activities.

hbase relies on "Zookeeper" to provide a message communication mechanism.

HBase – Hadoop Database is a highly reliable, high-performance, column-oriented, scalable distributed storage system that can be built on a cheap PC Server using HBase technology Build large-scale structured storage clusters.

ZooKeeper is a distributed, open source distributed application coordination service. It is an open source implementation of Google's Chubby and an important component of Hadoop and Hbase. It is a software that provides consistent services for distributed applications. The functions provided include: configuration maintenance, domain name services, distributed synchronization, group services, etc.

The relationship between hbase and zookeeper

hbase regionserver registers with zookeeper and tells zookeeper its status information (whether online or not). When hmaster starts, it will The system table is loaded into the zookeeper cluster, and the information of the current table can be obtained through zookeeper. The two communicate with each other. Zookeeper, as the cluster coordinator of hbase, coordinates and handles hbase activities.

zookeeper mainly has the following functions:

1. Configuration management:

can perform simple operations on all distributed machines. The desired configuration is simple and convenient.

2. Name service

is equivalent to a roster, remembering the names of all machines.

3. Cluster management

It is equivalent to asking zookeeper to allocate another machine for you after a machine that helps you do things hangs up.

Features of Zookeeper

1. Eventual consistency: Displaying the same view to the client is the most important function of zookeeper.

2. Reliability: If a message is accepted by one server, then it will be accepted by all servers.

3. Real-time performance: Zookeeper cannot guarantee that both clients can obtain the newly updated data at the same time. If the latest data is needed, the sync() interface should be called before reading the data.

4. Wait-free: Slow or failed clients do not interfere with fast client requests.

5. Atomicity: Updates can only succeed or fail, there is no intermediate state.

6. Sequence: All servers publish the same message in the same order.

The above is the detailed content of What does hbase rely on to provide message communication mechanism?. For more information, please follow other related articles on the PHP Chinese website!