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]: fail to search after upgrade from 2.3.15 to 2.4.1 and roll back to 2.3.15 #33242

Open
1 task done
yanliang567 opened this issue May 22, 2024 · 1 comment
Open
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@yanliang567
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.3.15->2.4.1->2.3.15
- Deployment mode(standalone or cluster): standalone
- MQ type(rocksmq, pulsar or kafka):

Current Behavior

  1. fail to search after rollback from 2.4.1 to 2.3.15
    pymilvus.exceptions.MilvusException: <MilvusException: (code=503, message=failed to query: node offline[node=2]: channel not available[channel=yanliang-2315-rootcoord-dml_1_449906074566018697v0])>
  2. it looks like knowhere is not able to handle a higher index version(built with 2.4.1)
    image

Expected Behavior

  1. search successfully

Steps To Reproduce

1. deploy a milvus 2.3.15
2. insert 200k 768d vectors, build hnsw and load
3. verify search successfully
4. upgrade to milvus 2.4.1
5. insert 500k more vectors 
6. verify search successfully
7. rollback to 2.3.15

Milvus Log

pod names in 4am

yanliang-2315-etcd-0                                              1/1     Running       0               23h     10.104.30.50    4am-node38   <none>           <none>
yanliang-2315-milvus-standalone-57fcfd6498-s9p49                  1/1     Running       0               14h     10.104.4.65     4am-node11   <none>           <none>
yanliang-2315-minio-5fd98575b7-xxhmq                              1/1     Running       0               23h     10.104.20.18    4am-node22   <none>           <none>

Anything else?

No response

@yanliang567 yanliang567 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 22, 2024
@yanliang567 yanliang567 self-assigned this May 22, 2024
@yanliang567
Copy link
Contributor Author

/assign @foxspy
/unassign

@sre-ci-robot sre-ci-robot assigned foxspy and unassigned yanliang567 May 22, 2024
@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 May 22, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.2, 2.4.3 May 22, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.3, 2.4.4, 2.4.5 May 30, 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/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants