From 8b76a8fa3006f863d998e7bec015011dcd368dac Mon Sep 17 00:00:00 2001 From: "min.tian" Date: Mon, 27 Sep 2021 16:21:59 +0800 Subject: [PATCH] [skip ci] Fix some writing problems (#8672) Signed-off-by: min.tian --- docs/developer_guides/chap01_system_overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developer_guides/chap01_system_overview.md b/docs/developer_guides/chap01_system_overview.md index ea85760eb3..0a48ff597d 100644 --- a/docs/developer_guides/chap01_system_overview.md +++ b/docs/developer_guides/chap01_system_overview.md @@ -38,7 +38,7 @@ The query/write nodes are linked to the hash ring, with each node covers some po The query nodes hold all the indexes in memory. Since building an index is time-consuming, the query nodes will dump their index to disk (store engine) for fast failure recovery and cross node index copy. -The write nodes are stateless. They simply transform the newly arrived WALs to binlog format, then append the binlog to store engine. +The write nodes are stateless. They simply transform the newly arrived WALs to binlog format, then append the binlog to the store engine. Note that not all the components are necessarily replicated. The system provides failure tolerance by maintaining multiple copies of WAL and binlog. When there is no in-memory index replica and there occurs a query node failure, other query nodes will take over its indexes by loading the dumped index files, or rebuilding them from binlog and WALs. The links from query nodes to the hash ring will also be adjusted such that the failure node's input WAL stream can be properly handled by its neighbors.