From 79f0889167db70f480447cdbdcadeb55c3b66d06 Mon Sep 17 00:00:00 2001 From: yanliang567 <82361606+yanliang567@users.noreply.github.com> Date: Wed, 22 Dec 2021 15:07:06 +0800 Subject: [PATCH] [skip e2e]Update milvus component names (#13958) Signed-off-by: yanliang567 --- .../root_coordinator_recovery_on_power_failure.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) 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 36088e14ef..3c426ba66c 100644 --- a/docs/design_docs/root_coordinator_recovery_on_power_failure.md +++ b/docs/design_docs/root_coordinator_recovery_on_power_failure.md @@ -42,20 +42,20 @@ - In the request processing function of `create index`, the call will return only when all segment ids have been sent `IndexCoord`. - Some segment ids may be sent to `IndexCoord` repeatedly, and `IndexCoord` needs to handle such requests. -### 2.4 New segment from `DC` +### 2.4 New segment from `DataCoord` -1. Each time a new segment is created, the `DC` sends the segment id to the `RC` via msgstream. -2. `RC` needs to update the segment id to the collection meta and record the position of the msgstream in etcd. +1. Each time a new segment is created, the `DataCoord` sends the segment id to the `RootCoord` via msgstream. +2. `RootCoord` needs to update the segment id to the collection meta and record the position of the msgstream in etcd. 3. Step 2 is transactional and the operation will be successful only if the collection meta in etcd is updated. -4. So the `RC` only needs to restore the msgstream to the position when recovering from a power failure. +4. So the `RootCoord` only needs to restore the msgstream to the position when recovering from a power failure. ### 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. -2. `RC` needs to fetch binlog from `DC` by id and send a request to `IC` to create an index on this segment. -3. When the `IC` is called successfully, it will return a build id, and then `RC` will update the build id to the `collection meta` and record the position of the msgstream in etcd. +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. -5. So the `RC` only needs to restore the msgstream to the position when recovering from a power failure. +5. So the `RootCoord` only needs to restore the msgstream to the position when recovering from a power failure. ### 2.6 Failed to call external grpc service