-
Notifications
You must be signed in to change notification settings - Fork 38
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]: run milvus-backup in k8s pod, retrurn "failed to connect \"Addr\": \"milvus:tcp:\" " #197
Comments
address should be a ip or a domain. |
"milvus" is correct in a Kubernetes context, it will resolve to the milvus-proxy pod, actually this look like a bug. In debug mode you can have the proof that "milvus" is correctly resolved but badly interpreted by sub-libraries :
Same issue using : milvus.my-namespace.svc.cluster.local I guess related code is : https://github.com/xushaoxiao/milvus-backup/blob/80c754eb9bfbb96961f244404ba7a3a5054d3e24/core/backup_context.go#L63C22-L63C50 The used func is deprecated as described in comment : https://github.com/milvus-io/milvus-sdk-go/blob/master/client/client.go#L285 No issue with v0.3.2
|
It is definitely a bug. Add PORT# at the tail of the address. Something likes this:
It will comment |
Yup it is definitely a bug. For me workaround is to set the port using |
/assign |
Current Behavior
When I run milvus-backup command on k8s pod, the target milvus address is wrong.
in backup.yaml:
milvus:
address: milvus
port: 19530
authorizationEnabled: false
in log:
[2023/09/08 07:35:33.943 +00:00] [INFO] [logutil/logutil.go:165] ["Log directory"] [configDir=]
[2023/09/08 07:35:33.943 +00:00] [INFO] [logutil/logutil.go:166] ["Set log file to "] [path=logs/backup.log]
[2023/09/08 07:35:33.943 +00:00] [INFO] [core/backup_impl_create_backup.go:25] ["receive CreateBackupRequest"] [requestId=4b980b8b-4e1a-11ee-8398-82b39bdfe663] [backupName=backup] [collections="[]"] [databaseCollections=] [async=false]
[2023/09/08 07:35:34.168 +00:00] [WARN] [grpclog/grpclog.go:46] ["[core][Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {\n "Addr": "milvus:tcp:",\n "ServerName": "milvus:tcp:",\n "Attributes": null,\n "BalancerAttributes": null,\n "Type": 0,\n "Metadata": null\n}. Err: connection error: desc = "transport: Error while dialing dial tcp: address milvus:tcp:: too many colons in address""]
Expected Behavior
expect connect to:
milvus:19530
Steps To Reproduce
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: