Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Load collection failed #38540

Open
1 task done
tosone opened this issue Dec 17, 2024 · 2 comments
Open
1 task done

[Bug]: Load collection failed #38540

tosone opened this issue Dec 17, 2024 · 2 comments
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@tosone
Copy link

tosone commented Dec 17, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

Cannot load collection. Load collection api no response.

Expected Behavior

Load collection correctly.

Steps To Reproduce

1. create collection.
2. create index.
3. load collection.
4. insert data.

after a short time. then:
5. collection status become 'recovering'
6. I tried release the collection.
7. try to load collection, but failed.

The collection id is collectionID=454420645450765444

Milvus Log

logs.tar.gz

Anything else?

No response

@tosone tosone added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 17, 2024
@yanliang567
Copy link
Contributor

/assign @congqixia
/unassign

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 19, 2024
@congqixia
Copy link
Contributor

from the log you provide:

  1. there are five active pod alive but non of them are ACTIVE querycoord
  2. the suspicious load operation happened 2024/12/17 12:21:39.412 +00:00 but no related load request is found in proxy log or querycoord log

could you please upgrade your server to v2.4 latest and try to load again? If the problem persist, please attach the log from latest requests, thanks~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants