Mysql集群方案(一) - Cluster & Replication 介绍
2011-07-22 23:32
597 查看
对数据库集群处于初步学习阶段,记录备忘
扫盲:
提到Mysql集群(Mysql Cluster),其实有两类方案, 名字上的Mysql Cluster只是其中一类.
Mysql Cluster 将数据放内存中
A MySQL Cluster consists of a set of computers, each running a one or more processes which may include a MySQL server, a data node, a management server, and (possibly) a specialized data access programs. The relationship of these components in a cluster is shown here:
如上图,这个系统中,最小的集群可能是如此:
topology
Replication - Read/Write
Replication - Separate Read & Write
Using replication to improve the performance during scaleout
Comparison
http://haka.sharera.com/blog/BlogTopic/54291.htm
扫盲:
提到Mysql集群(Mysql Cluster),其实有两类方案, 名字上的Mysql Cluster只是其中一类.
Mysql Cluster 将数据放内存中
A MySQL Cluster consists of a set of computers, each running a one or more processes which may include a MySQL server, a data node, a management server, and (possibly) a specialized data access programs. The relationship of these components in a cluster is shown here:
如上图,这个系统中,最小的集群可能是如此:
Node | IP Address |
Management (MGM) node | 192.168.0.10 |
MySQL server (SQL) node | 192.168.0.20 |
Data (NDBD) node "A" | 192.168.0.30 |
Data (NDBD) node "B" | 192.168.0.40 |
Replication - Read/Write
Replication - Separate Read & Write
Using replication to improve the performance during scaleout
Comparison
Requirements | MySQL Replication | MySQL Replication + Heartbeat | MySQL Heartbeat + DRBD | MySQL Cluster |
---|---|---|---|---|
Availability | ||||
Automated IP failover | No | Yes | Yes | No |
Automated database failover | No | No | Yes | Yes |
Typical failover time | User/script-dependent | Varies | < 30 seconds | < 3 seconds |
Automatic resynchronization of data | No | No | Yes | Yes |
Geographic redundancy support | Yes | Yes | Yes, when combined with MySQL Replication | Yes, when combined with MySQL Replication |
Scalability | ||||
Built-in load balancing | No | No | No | Yes |
Supports Read-intensive applications | Yes | Yes | Yes, when combined with MySQL Replication | Yes |
Supports Write-intensive applications | No | No | Yes | Yes |
Maximum number of nodes per group | One master, multiple slaves | One master, multiple slaves | One active (primary), one passive (secondary) node | 255 |
Maximum number of slaves | Unlimited (reads only) | Unlimited (reads only) | One (failover only) | Unlimited (reads only) |
相关文章推荐
- MySQL高可用方案之集群(Cluster)
- mysql-cluster集群原理介绍和搭建步骤(四个data/sql节点)
- 系统间通信方式之(ActiveMQ的集群方案介绍结束2之高潮部分了【(1master+2slave)*cluster】)(十九)
- MySql从一窍不通到入门(八)复制(replication)和集群(cluster)/读写分离
- MySQL Fabric、 MySQL分片高可用集群之MySQL Cluster、 较成熟的集群方案Galera Cluster的部署使用优缺点
- mysql集群方案整理之Galera Cluster简介
- 【完美】Mysql-cluster数据库集群-介绍
- mysql-cluster集群原理介绍和搭建步骤(四个data/sql节点) (转)
- mysql高可用方案之集群(cluster)
- mysql replication cluster 双机热备集群搭建及常见错误排除
- mysql-cluster集群原理介绍和搭建步骤(四个data/sql节点)
- 安装mysql-cluster-gpl-7.2二进制版本 及 设置ndb集群
- mysql 分布式集群方案
- 集群(cluster)基础知识介绍
- MySQL实时在线备份恢复方案:Replication+LVM Snapshot【上篇】
- 详解 MySQL Replication Error 1032 & 1205
- hadoop 集群环境Sqoop 将数据导入mysql问题 many connection errors; unblock with 'mysqladmin flush-hosts'
- 使用Micrisoft.net设计方案 第三章Web表示模式 Web模式集群详细介绍 Page Cache(页面缓存)
- 分布式MySQL集群方案的探索与思考
- 集群(cluster)&高可用性(HA)概念