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]: Should determine the obj storage service provider based on address for compatibility #27905

Closed
1 task done
czs007 opened this issue Oct 25, 2023 · 1 comment
Closed
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@czs007
Copy link
Collaborator

czs007 commented Oct 25, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

The latest version of Milvus is unable to create the MinioClient correctly under GCP.

Expected Behavior

The previous version of Milvus (2.2.14) did not include the cloud provider information in the create index requests sent to index worker. Therefore, the new index worker (Milvus) needs to be able to differentiate between different object storage providers based on the service address.

Steps To Reproduce

1. deploying Milvus on GCP, the index node should be selected as version 2.3 of Milvus, while the other roles should use version 2.2.x of Milvus
2. try to create index

Milvus Log

No response

Anything else?

No response

@czs007 czs007 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 Oct 25, 2023
@czs007 czs007 self-assigned this Oct 25, 2023
@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 Oct 25, 2023
@yanliang567 yanliang567 added this to the 2.3.2 milestone Oct 25, 2023
@yanliang567 yanliang567 modified the milestones: 2.3.2, 2.3.3 Nov 3, 2023
@yanliang567 yanliang567 modified the milestones: 2.3.3, 2.3.4 Nov 16, 2023
Copy link

stale bot commented Dec 17, 2023

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.

@stale stale bot added the stale indicates no udpates for 30 days label Dec 17, 2023
@stale stale bot closed this as completed Dec 24, 2023
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 stale indicates no udpates for 30 days 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