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

[skip ci]Update etcd in offical naming (#9843)

Browse Source 
Signed-off-by: yanliang567 <yanliang.qiao@zilliz.com>
This commit is contained in:
yanliang567 2021-10-14 09:36:33 +08:00 committed by GitHub
parent 404b3710ff
commit 964c8ff414
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/design_docs/index_design.md
View File

@ -29,7 +29,7 @@ IndexCoordinate receives requests from RootCoordinate to build an index, delete
In Milvus, index building is performed asynchronously. When IndexCoordinate receives a request to build an index from
RootCoordinate, it will first check whether the same index has been created according to the parameters. If the same
index has been created, it will return the IndexBuildID of the existing task. Otherwise, assign a globally unique
IndexBuildID to the task, then records the task in the MetaTable, and writes the MetaTable to the ETCD, and then
IndexBuildID to the task, then records the task in the MetaTable, and writes the MetaTable to the etcd, and then
returns it to RootCoordinate. At this point, RootCoordinate already knows that it has successfully sent the task to
IndexCoordinate. In fact, the index construction has not been completed yet. IndexCoordinate will have a background
process to find all the index tasks that need to be allocated periodically, and then allocate them to IndexNode for