test/milvus
1
0
Fork 0
mirror of https://gitee.com/milvus-io/milvus.git synced 2024-12-02 03:48:37 +08:00
Code Issues Actions 12 Packages Projects Releases Wiki Activity

[skip ci]Update full name of milvus component (#13049)

Browse Source 
Signed-off-by: yanliang567 <yanliang.qiao@zilliz.com>
This commit is contained in:
yanliang567 2021-12-09 14:25:06 +08:00 committed by GitHub
parent 5f75face4a
commit 55c76f202d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/design_docs/drop_collection_release_resources_en.md
View File

@ -28,18 +28,18 @@ DataNode ignites Flush&Drop
Add a `dropped` flag in `SaveBinlogPathRequest` proto
DN
DataNode
- Flush all segments in this vChannel, When Flush&Drop, set the `dropped` flag true.
- If fails, retry at most 10 times and restart
DC
DataCoord
- DataCoord marks segmentInfo as `dropped`, doesn't remove segmentInfos from etcd
- When recovery, check if the segments in the vchannel are all dropped
- if not, recover before the drop
- if so, no need to recover the vchannel
Pros:
1. The easiest approach in both DN and DC
1. The easiest approach in both DataNode and DataCoord
2. DN can reuse the current flush manager procedure
Cons:
1. The No. rpc call is equal to the No. segments in a collection, expensive