[skip ci]Refine the format of index doc (#10183)

Signed-off-by: yanliang567 <yanliang.qiao@zilliz.com>
pull/10190/head
yanliang567 2021-10-19 17:04:43 +08:00 committed by GitHub
parent edf3377fe1
commit d41ce157bc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 5 deletions

View File

@ -42,17 +42,22 @@ deleted from the MetaTable.
When IndexCoordinate receives a query index status request from other components, first check whether the corresponding
index task is marked for deletion in the MetaTable. If marked for deletion, the return index does not exist, otherwise,
it returns the index information
it returns the index information.
## 8.3 Feature Design
IndexCoord has two main structures, NodeManager and MetaTable. NodeManager is used to manage IndexNode node information,
and MetaTable is used to maintain index related information.
IndexCoord mainly has these functions: `watchNodeLoop`, `watchMetaLoop`, `assignTaskLoop` and `recycleUnusedIndexFiles`.
`watchNodeLoop` is mainly responsible for monitoring the changes of IndexNode nodes, `watchMetaLoop` is mainly
responsible for monitoring the changes of Meta, `assignTaskLoop` is mainly responsible for assigning index building tasks,
and `recycleUnusedIndexFiles` is mainly responsible for cleaning up useless index files and deleted index records.
IndexCoord mainly has these functions:
`watchNodeLoop` is mainly responsible for monitoring the changes of IndexNode nodes;
`watchMetaLoop` is mainly responsible for monitoring the changes of Meta;
`assignTaskLoop` is mainly responsible for assigning index building tasks;
`recycleUnusedIndexFiles` is mainly responsible for cleaning up useless index files and deleted index records;
### 8.3.1 The relationship between IndexCoord and IndexNode