SimFG
SimFG
you can try to set the `consistency_level` param to `Strong` in the delete method
@dushulin maybe the go sdk have not give the param, you can set the collection `consistency_level ` to `strong`, and try to delete the data.
@congqixia please give this issue a look
@dushulin you can set the `consistency_level` in search and query request https://github.com/milvus-io/milvus-sdk-go/blob/e697167f1828049c4c6237f0e3646b77b725ebdf/client/options.go#L174-L179
here is the client api ``` func (c *GrpcClient) Search(ctx context.Context, collName string, partitions []string, expr string, outputFields []string, vectors []entity.Vector, vectorField string, metricType entity.MetricType, topK int, sp entity.SearchParam, opts...
@dushulin you can try to use the attu to delete the data. And the http api currently does not support this parameter, because it's a new parameter.
@ThreadDao you can try to use the latest 2.3 branch to build a image, it should have been fixed. link pr: https://github.com/milvus-io/milvus/pull/29557
@ThreadDao This is caused by too many dropped segments, which means the cleaning speed is relatively slow and it blocks the GC
@ThreadDao @chyezh From the server log, i found it maybe block the recycle unused indexes step. [loglink](https://grafana-4am.zilliz.cc/explore?orgId=1&left=%7B%22datasource%22:%22Loki%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22%7Bnamespace%3D%5C%22qa-milvus%5C%22,pod%3D~%5C%22laion1b-test-2-milvus-mixcoord-.*%5C%22%7D%20%7C~%20%5C%22start%20recycleUnusedIndexes%7Cstart%20recycleUnusedIndexFiles%7Cgarbage%20collector%20paused%7CsegmentID%20is%20not%20in%20drops%7Cskipping%20GC%7Cdropped%20segment%20dml%20position%20after%20channel%20cp%5C%22%22%7D%5D,%22range%22:%7B%22from%22:%221704151440000%22,%22to%22:%221704225600000%22%7D%7D)