mirror of https://github.com/milvus-io/milvus.git
[skip ci] Fix the spell of etcd in design doc (#9804)
Signed-off-by: Edward Zeng <jie.zeng@zilliz.com>pull/9806/head
parent
6b8f472839
commit
c3c82886a7
|
@ -26,7 +26,7 @@ So what's DataNode's starting procedure?
|
|||
|
||||
### 1. Serveice Registration
|
||||
|
||||
DataNode registers itself to Etcd after grpc server started, in *INITIALIZING* state.
|
||||
DataNode registers itself to etcd after grpc server started, in *INITIALIZING* state.
|
||||
|
||||
### 2. Service Discovery
|
||||
|
||||
|
@ -50,9 +50,9 @@ keep the vchannel states update.
|
|||
|
||||
## Some of the following interface/proto designs are outdated, will be updated soon
|
||||
|
||||
### 1. DataNode no longer interacts with Etcd except service registering
|
||||
### 1. DataNode no longer interacts with etcd except service registering
|
||||
|
||||
#### DataCoord rather than DataNode saves binlog paths into Etcd
|
||||
#### DataCoord rather than DataNode saves binlog paths into etcd
|
||||
|
||||

|
||||
|
||||
|
@ -134,7 +134,7 @@ type dataSyncService struct {
|
|||
}
|
||||
```
|
||||
|
||||
DataNode Init -> Resigter to Etcd -> Discovery data service -> Discover master service -> IDLE
|
||||
DataNode Init -> Resigter to etcd -> Discovery data service -> Discover master service -> IDLE
|
||||
|
||||
WatchDmChannels -> new dataSyncService -> HEALTH
|
||||
|
||||
|
|
Loading…
Reference in New Issue