mirror of https://github.com/milvus-io/milvus.git
[skip ci]Update docs about datanode recovery design (#11627)
Signed-off-by: shiyu22 <shiyu.chen@zilliz.com>pull/11637/head
parent
89c17c265b
commit
4b1d414329
|
@ -6,16 +6,15 @@ update: 6.21.2021, by [Goose](https://github.com/XuanYang-cn)
|
|||
|
||||
## What's DataNode?
|
||||
|
||||
DataNode processes insert data and persists them.
|
||||
DataNode processes insert data and persist them.
|
||||
|
||||
DataNode is based on flowgraph; each flowgraph cares about only one vchannel. There are ddl messages, dml
|
||||
messages, and timetick messages inside one vchannel, FIFO log stream.
|
||||
|
||||
One vchannel only contains dml messages of one collection. A collection consists of many segments, hence
|
||||
a vchannel contains dml messages of many segments. **Most importantly, the dml messages of the same segment
|
||||
can appear in anywhere in vchannel.**
|
||||
a vchannel contains dml messages of many segments. **Most importantly, the dml messages of the same segment can appear anywhere in vchannel.**
|
||||
|
||||
## What does DataNode recovery really mean?
|
||||
## What is the real meaning of DataNode recovery?
|
||||
|
||||
DataNode is stateless, but vchannel has states. DataNode's statelessness is guaranteed by DataCoord, which
|
||||
means the vchannel's state is maintained by DataCoord. So DataNode recovery is no different from starting.
|
||||
|
|
Loading…
Reference in New Issue