[Bug]: milvus query is hang

[liuzh-sa]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

- Milvus version: 2.4.4
- Deployment mode(standalone or cluster): cluster
- MQ type(rocksmq, pulsar or kafka):    pulsar
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

query hang

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

milvus-log.tar.gz

Anything else?

No response

[xiaofan-luan]

file/delta_log/451293960015077677/451293960015077678/451293960016289982/451792976385935885

there seems to be some delta log missing..

you probably need to check the log on how many files are missing. If there are only 1-2 files missing maybe simply use birdwatcher to remove the meta.

[liuzh-sa]

file/delta_log/451293960015077677/451293960015077678/451293960016289982/451792976385935885

there seems to be some delta log missing..

you probably need to check the log on how many files are missing. If there are only 1-2 files missing maybe simply use birdwatcher to remove the meta.

How to delete？

[congqixia]

@liuzh-sa

1. how to check how many files is missing birdwatcher has a command to scan all missing file verify-segment --collection [colleciton_id]

2. use remove binlog to remove error binlog if found

[liuzh-sa]

1. verify-segment --collection

Do we need to delete all of these?

[yanliang567]

/assign @congqixia /unassign

[xiaofan-luan]

1. verify-segment --collection

Do we need to delete all of these?

seems that you are missing a lot of data.

Could you explain what operation you did to this cluster?

[liuzh-sa]

1. verify-segment --collection

Do we need to delete all of these?

seems that you are missing a lot of data.

Could you explain what operation you did to this cluster?

We imported data into the cluster. Before the import started, the cluster became unreadable. Then we restarted the cluster and that was it.

[liuzh-sa]

小龙 understands the situation of our cluster.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.