Mysql主从与集群的区别
2015-12-26 14:53
519 查看
In traditional MySQL replication, a master MySQL server updates one or more slaves. Transactions are committed sequentially, and a slow transaction can cause the slave to lag behind the master. This means that if the master fails, it is possible that the slave
might not have recorded the last few transactions. If a transaction-safe engine such as InnoDB is being used, a transaction will either be complete on the slave or not applied at all, but replication does not guarantee that all data on the master and the slave
will be consistent at all times. In MySQL Cluster, all data nodes are kept in synchrony, and a transaction committed by any one data node is committed for all data nodes. In the event of a data node failure, all remaining data nodes remain in a consistent
state.
In short, whereas standard MySQL replication is asynchronous, MySQL Cluster is synchronous.
We have implemented (asynchronous) replication for Cluster in MySQL 5.1 and later. MySQL Cluster Replication (also sometimes known as “geo-replication”) includes the capability to replicate both between two MySQL Clusters, and from a MySQL Cluster to a non-Cluster
MySQL server. However, we do not plan to backport this functionality to MySQL 5.1. See Section 17.6, “MySQL Cluster Replication”.
might not have recorded the last few transactions. If a transaction-safe engine such as InnoDB is being used, a transaction will either be complete on the slave or not applied at all, but replication does not guarantee that all data on the master and the slave
will be consistent at all times. In MySQL Cluster, all data nodes are kept in synchrony, and a transaction committed by any one data node is committed for all data nodes. In the event of a data node failure, all remaining data nodes remain in a consistent
state.
In short, whereas standard MySQL replication is asynchronous, MySQL Cluster is synchronous.
We have implemented (asynchronous) replication for Cluster in MySQL 5.1 and later. MySQL Cluster Replication (also sometimes known as “geo-replication”) includes the capability to replicate both between two MySQL Clusters, and from a MySQL Cluster to a non-Cluster
MySQL server. However, we do not plan to backport this functionality to MySQL 5.1. See Section 17.6, “MySQL Cluster Replication”.
相关文章推荐
- 关于远程访问mysql出现Access denied for user 'root'@'的解决方法
- Mysql自增主键归零的方法
- Mysql中怎样返回一个数据库的所有表名,列名数据类型备注
- MySQL数据库系统
- InnoDB: Error: innodb_table_stats not found索引表没找到,主从停止
- mysql:百度地图经纬度,按照经纬度坐标排序查询
- [Mysql for Excel指南] 第二章 安装
- ubuntu 15.04 编译安装 mysql 5.5.44
- Mysql入门实战上
- [实战]MVC5+EF6+MySql企业网盘实战(21)——网盘操作日志
- 数据库 --> MySQL使用
- Mysql for Excel安装
- 添加PATH
- [mysql for excel指南] 第一章 介绍
- 【MySQL】常用MySQL语句
- 数据库表结构对比同步mysqldiff
- 常用MySQL语句
- mysql导入btree错误解决方法
- mysql函数大全
- mysql 查询数据库的表名 列名