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

Client connection to Zilliz from non-local deployment error #413

Open
lairdkruger opened this issue Jan 22, 2025 · 0 comments
Open

Client connection to Zilliz from non-local deployment error #413

lairdkruger opened this issue Jan 22, 2025 · 0 comments

Comments

@lairdkruger
Copy link

lairdkruger commented Jan 22, 2025

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:

  1. Create a cluster and collection on Zilliz
  2. Copy this repo: https://github.com/lairdkruger/milvus-zilliz-client-server-connection-issue
  3. Test that the local instance connect succesfully
  4. Deploy to Deno Deploy
  5. 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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant