From ff79f883a9e96b44fd8d6d6d31f79af6415dae77 Mon Sep 17 00:00:00 2001 From: yanliang567 <82361606+yanliang567@users.noreply.github.com> Date: Tue, 28 Dec 2021 14:14:16 +0800 Subject: [PATCH] [skip e2e]Update milvus component names (#14408) Signed-off-by: yanliang567 --- docs/design_docs/root_coordinator_recovery_on_power_failure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design_docs/root_coordinator_recovery_on_power_failure.md b/docs/design_docs/root_coordinator_recovery_on_power_failure.md index 54bb535a1c..f9ad534a0f 100644 --- a/docs/design_docs/root_coordinator_recovery_on_power_failure.md +++ b/docs/design_docs/root_coordinator_recovery_on_power_failure.md @@ -51,7 +51,7 @@ ### 2.5 Flushed segment from `data node` -1. Each time the `data node` finishes flushing a segment, it sends the segment id to the `RC` via msgstream. +1. Each time the `DataNode` finishes flushing a segment, it sends the segment id to the `RootCoord` via msgstream. 2. `RootCoord` needs to fetch binlog from `DataCoord` by id and send a request to `IndexCoord` to create an index on this segment. 3. When the `IndexCoord` is called successfully, it will return a build id, and then `RootCoord` will update the build id to the `collection meta` and record the position of the msgstream in etcd. 4. Step 3 is transactional and the operation will be successful only if the `collection meta` in etcd is updated.