milvus-io
/
milvus
mirror of https://github.com/milvus-io/milvus.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[skip ci] Fix some writing problems (#8549) 

Signed-off-by: min.tian <min.tian.cn@gmail.com>
pull/8569/head
min.tian 2021-09-26 12:44:13 +08:00 committed by GitHub
parent 6168c0b9c7
commit 5e87c3a932
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/developer_guides/chap01_system_overview.md
View File

@ -36,7 +36,7 @@ The WAL forms a hash ring. Requests (i.e. inserts and deletes) from clients will
The query/write nodes are linked to the hash ring, with each node covers some portion of the buckets. Once the hash function and bucket coverage are settled, the chain 'proxy -> WAL -> query/write node' will act as a producer-consumer pipeline. Logs in each bucket is a determined operation stream. Via performing the operation stream in order, the query nodes keep themselves up to date.
The query nodes hold all the indexes in memory. Since building 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 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.