admin/milvus
1
0
Fork 0
mirror of https://gitee.com/milvus-io/milvus.git synced 2026-01-07 19:31:51 +08:00
Code Issues Packages Projects Releases Wiki Activity

[skip ci]Refine index design doc (#10008)

Browse Source 
Signed-off-by: yanliang567 <yanliang.qiao@zilliz.com>
This commit is contained in:
yanliang567 2021-10-16 21:53:34 +08:00 committed by GitHub
parent a4a66341da
commit f1b965fbf5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/design_docs/index_design.md
View File

@ -27,13 +27,12 @@ state after power off and restart.
IndexCoordinate receives requests from RootCoordinate to build an index, delete an index, and query the status of an index.
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
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
actual execution.
RootCoordinate, it will first check whether the same index has been created according to the index parameters. If yes, it would
return the IndexBuildID of the existing task. Otherwise, it would assign a globally unique IndexBuildID to the task,
record the task in the MetaTable, write the MetaTable to etcd, and then return the IndexBuildID to RootCoordinate.
RootCoordinate confirms the index building was generated successfully by the IndexBuildID. At this time, the index construction
is completed yet. IndexCoordinate starts a background process to find all the index tasks that need to be
allocated periodically, and then allocates them to IndexNode for actual execution.
When IndexCoordinate receives a request to delete an index from RootCoordinate, IndexCoordinate traverses the MetaTable,
marks the corresponding index task as deleted, and returns. It is not really deleted from the MetaTable at this time.