Client connection to Zilliz from non-local deployment error #413
Description
Describe the bug:
When creating a Milvus Client connection to Zilliz Cluster from a non-local environment:
Error: 14 UNAVAILABLE: No connection established. Last error: connect ECONNREFUSED
This is the main error that I'm facing.
The issue is that my local project connects, but from a serverless function, or server, I get the message above.
I've tried using cluster tokens, and username/password for authentication - both working fine locally, same error when deployed.
Steps to reproduce:
- Create a cluster and collection on Zilliz
- Copy this repo: https://github.com/lairdkruger/milvus-zilliz-client-server-connection-issue
- Test that the local instance connect succesfully
- Deploy to Deno Deploy
- Test that the Deno deployment has the connection issues (error message above)
Milvus-node-sdk version:
npm:@zilliz/milvus2-sdk-node@^2.5.4
Milvus version:
Zilliz Compatible With Milvus 2.4.x
I'm not 100% sure this is a bug, but hoping somebody can help out on hosting a client from a non-local environment.
I've ran into, and attempted to debug the following setups so far this week:
- I've tried the Python SDK on Vercel: (serverless function memory limit reached)
- Node.js on Vercel: (⨯ Error: ENOENT: no such file or directory, open '/var/task/node_modules/.pnpm/@zilliz[email protected]/node_modules/@zilliz/milvus2-sdk-node/dist/proto/proto/common.proto')
- Node.js with NextJS (pretty much the same as above but I copied this project setup and still got the same error as above)
- Deno on Deno Deploy (the main issue I'm referencing here)
I also understand that this could be an issue with Deno, Deno Deploy, Milvus, Zilliz. My guess is that it's related to GRPC connections on Deno Deploy, or something security/certificate related.
Appreciate any help :)