Merge pull request #2846 from taosdata/Aries-Lee1991-patch-12

Update replica-ch.md
This commit is contained in:
Yiqing Liu 2020-07-31 19:09:20 +08:00 committed by GitHub
commit 4a78d2fb99
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

View File

@ -105,7 +105,7 @@ TDengine采取的是Master-Slave模式进行同步与流行的RAFT一致性
如果vnode A是master, vnode B是slave, vnode A能接受客户端的写请求而vnode B不能。当vnode A收到写的请求后遵循下面的流程
<center> <img src="../assets/replica-forward.jpg"> </center>
<center> <img src="../assets/replica-forward.png"> </center>
1. 应用对写请求做基本的合法性检查,通过,则给改请求包打上一个版本号(version, 单调递增)
2. 应用将打上版本号的写请求封装一个WAL Head, 写入WAL(Write Ahead Log)
@ -140,7 +140,7 @@ TDengine采取的是Master-Slave模式进行同步与流行的RAFT一致性
整个数据恢复流程分为两大步骤第一步先恢复archived data(file), 然后恢复wal。具体流程如下
<center> <img src="../assets/replica-restore.jpg"> </center>
<center> <img src="../assets/replica-restore.png"> </center>
1. 通过已经建立的TCP链接发送sync req给master节点
2. master收到sync req后以client的身份向vnode B主动建立一新的专用于同步的TCP链接syncFd)