Shulou(Shulou.com)05/31 Report--

What are the characteristics and architecture advantages and disadvantages of MariaDB Codership Galera Cluster? I believe many inexperienced people don't know what to do about it. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

Codership Galera Cluster has the following characteristics:

Fully synchronous replication, transactions are either committed on all nodes, then all are rolled back.

Multi-master replication, which can be written at any node.

Applying events in parallel from the server is a real parallel replication.

The node is automatically configured and the failed node is automatically removed from the cluster. When the failed node joins the cluster again, there is no need to manually back up the current database and copy it to the failed node.

Synchronization has no delay, which can ensure the consistency of data.

It has application compatibility, does not need to change the application, and has a native MySQL interface.

Each node contains a complete copy of the data.

The synchronous replication of each node is not achieved through binlog, but through galera.cache.

Points to pay attention to:

In the production environment, it is recommended that the cluster be configured with three nodes, otherwise it is easy to have brain fissure.

The advantages of Galera Cluster architecture are as follows:

It is a true multi-master architecture, and any node can read and write without the separation of read and write.

Without centralized management, any node can be lost at any point in time, and the normal work of the cluster will not be affected.

Node downtime does not result in data loss.

Transparent to the application, no changes to the application or only minimal changes.

The disadvantages of the Galera Cluster architecture are as follows:

It is expensive to join a new node and it is necessary to copy the complete data.

The problem of write extension cannot be solved effectively, and all write operations will occur on all nodes.

There are as many duplicated data as there are nodes.

Because transaction commit requires cross-node communication (distributed transactions), writes are much slower than master-slave replication, writes become slower and slower, and natural deadlocks and rollbacks become more frequent as the number of cluster nodes increases.

The requirement for the network is very high. If the network fluctuates or the computer room is attacked by ARP, the two nodes will be lost, the Galera Cluster cluster will have a brain fissure, and the service will be unavailable.

After reading the above, have you mastered the features and architectural advantages and disadvantages of MariaDB Codership Galera Cluster? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.