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]: collection can not loaded when restart after server's sudden electricity lost #33145

Open
1 task done
James-ge opened this issue May 18, 2024 · 2 comments
Open
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@James-ge
Copy link

James-ge commented May 18, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

  1. after restart, server consistently print warn log 'failed to get collection rate limit config' with the same collectionID=449844857107126063
  2. collection can not be load correctly
    warn_and_error_log.log

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@James-ge James-ge 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 May 18, 2024
@xiaofan-luan
Copy link
Contributor

this seems to be an old bug already fixed, 449844857107126063 has been deleted but there are some meta left.
Try:

  1. upgrade to 2.3.15 seem it works?
  2. if now, use birdwatcher clean all the meta for 449844857107126063 on etcd. then the cluster should be able to load

@yanliang567
Copy link
Contributor

/assign @James-ge
/unassign

@sre-ci-robot sre-ci-robot assigned James-ge and unassigned yanliang567 May 20, 2024
@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 20, 2024
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/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants