未验证 提交 a17c63bc 编写于 作者: L Liang Zhang 提交者: GitHub

Update feature/master-slave document (#5839)

上级 ed1452f8
+++
pre = "<b>3.3.2. </b>"
title = "核心功能"
weight = 2
+++
1. 提供一主多从的读写分离配置,可独立使用,也可配合分库分表使用。
1. 独立使用读写分离支持SQL透传。
1. 同一线程且同一数据库连接内,如有写入操作,以后的读操作均从主库读取,用于保证数据一致性。
1. 基于Hint的强制主库路由。
\ No newline at end of file
+++
pre = "<b>3.3.2. </b>"
title = "Core Features"
weight = 2
+++
1. Provide the read-write split configuration of one master database with multiple slave databases, which can be used alone or with sharding table and database.
1. Support SQL pass-through in independent use of read-write split.
1. If there is write operation in the same thread and database connection, all the following read operations are from the master database to ensure data consistency.
1. Forcible master database route based on SQL Hint.
+++
pre = "<b>3.3.3. </b>"
title = "不支持项"
weight = 3
+++
1. 主库和从库的数据同步。
1. 主库和从库的数据同步延迟导致的数据不一致。
1. 主库双写或多写。
1. 跨主库和从库之间的事务的数据不一致。主从模型中,事务中读写均用主库。
\ No newline at end of file
+++
pre = "<b>3.3.3. </b>"
title = "Unsupported Items"
weight = 3
+++
1. Data replication between the master and the slave database.
1. Data inconsistency caused by replication delay between databases.
1. Double or multiple master databases to provide write operation.
1. The data for transaction across Master and Slave nodes are inconsitent. In the Master-Savle replication model, the master nodes need to be used for both reading and writing in the transaction.
\ No newline at end of file
+++
pre = "<b>3.3.2. </b>"
title = "使用规范"
weight = 2
+++
## 支持项
* 提供一主多从的读写分离配置,可独立使用,也可配合分库分表使用
* 独立使用读写分离支持SQL透传
* 同一线程且同一数据库连接内,如有写入操作,以后的读操作均从主库读取,用于保证数据一致性
* 基于Hint的强制主库路由
## 不支持项
* 主库和从库的数据同步
* 主库和从库的数据同步延迟导致的数据不一致
* 主库双写或多写
* 跨主库和从库之间的事务的数据不一致。主从模型中,事务中读写均用主库
+++
pre = "<b>3.3.2. </b>"
title = "Use Norms"
weight = 2
+++
## Supported Items
* Provide the read-write split configuration of one master database with multiple slave databases, which can be used alone or with sharding table and database.
* Support SQL pass-through in independent use of read-write split.
* If there is write operation in the same thread and database connection, all the following read operations are from the master database to ensure data consistency.
* Forcible master database route based on SQL Hint.
## Unsupported Items
* Data replication between the master and the slave database.
* Data inconsistency caused by replication delay between databases.
* Double or multiple master databases to provide write operation.
* The data for transaction across Master and Slave nodes are inconsistent. In the Master-Slave replication model, the master nodes need to be used for both reading and writing in the transaction.
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册