Introduction to Master / Slave
主人/奴隶介绍。
The following are the different kinds of Master/Slave configurations available:
以下是不同类型的主/从配置:
Master Slave Type 主从式 |
Requirements 需求 |
Pros 优点 |
Cons 缺点 |
Shared File System Master Slave 共享文件系统主从。 |
A shared file system such as a SAN 共享文件系统，如SAN。 |
Run as many slaves as required. Automatic recovery of old masters 按要求运行大量的奴隶。自动恢复老主人。 |
Requires shared file system 需要共享文件系统 |
JDBC Master Slave JDBC主从 |
A Shared database 一个共享数据库 |
Run as many slaves as required. Automatic recovery of old masters 按要求运行大量的奴隶。自动恢复老主人。 |
Requires a shared database. Also relatively slow as it cannot use the high performance journal 需要一个共享数据库。也相对较慢，因为它不能使用高性能日志。 |
Replicated LevelDB Store 复制并且存储 |
ZooKeeper Server 动物园管理员服务器 |
Run as many slaves as required. Automatic recovery of old masters. Very fast. 按要求运行大量的奴隶。自动恢复老主人。非常快。 |
Requires a ZooKeeper server. 需要一个动物园管理员服务器。 |
If you are using a shared network file system such as a SAN we recommend a Shared File System Master Slave. If you are happy to dispense with the high performance journal and are using pure JDBC as your persistence engine then you should use JDBC Master Slave instead. For those willing to try out new tech, the Replicated LevelDB Store gives speeds similar to a SAN solution without the hassle of having to setup a highly available shared file system.
如果您使用的是共享网络文件系统，比如SAN，我们推荐共享文件系统主服务器。如果您乐于放弃高性能日志，并且使用纯JDBC作为持久性引擎，那么您应该使用JDBC主从。对于那些愿意尝试新技术的人来说，复制的LevelDB商店提供了类似SAN解决方案的速度，省去了设置高可用共享文件系统的麻烦。