milvus-io/milvus-sdk-node

Fail to run langchain milvus vector store sample

webup opened this issue · 9 comments

webup commented

Describe the bug:

Fail to run this sample with error messages: E Connection to dns:in03-02861d92d812d64.api.gcp-us-west1.zillizcloud.com at 34.160.220.160:443 rejected by server because of excess pings.

Steps to reproduce:

image

Milvus-node-sdk version: 2.2.23

Milvus version: Ziliz Cloud Serverless (Free)

looks like there is an issue on the server, we will investigate it.

webup commented

looks like there is an issue on the server, we will investigate it.

any updates? :)

looks like there is an issue on the server, we will investigate it.

any updates? :)

Would you try the dedicated server? serverless may have some problem on langchain.js. it needs to be update.

webup commented

looks like there is an issue on the server, we will investigate it.

any updates? :)

Would you try the dedicated server? serverless may have some problem on langchain.js. it needs to be update.

Got you, dedicated server works. Looking forward to the serverless update. 💪

webup commented

Hi there, any updates or further guides on the server side?

I've noticed and tried latest milvus client update on langchain-js, still not working w/ serverless server. :(

@nameczz could you please give an example?

@webup Hi, we update example now. Please have a check.

webup commented

@webup Hi, we update example now. Please have a check.

I've updated langchain and milvus lib to the latest, and followed this ut as the sample which should be same as your langchain.js sample, but still failed to connect the server.

  new OpenAIEmbeddings(),
  {
    collectionName: "langchain_valtown",
    // autoId: false,
    // primaryField: "id",
    clientConfig: {
      address: process.env.ZILIZ_URL,
      token: process.env.ZILIZ_API_KEY,
      ssl: true,
    },
  }

Following error messages returned:

(node:83380) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
Error: 14 UNAVAILABLE: No connection established
    at callErrorFromStatus (/Users/haili/workspaces/lab/langchain-js/node_modules/.pnpm/@grpc+grpc-js@1.8.17/node_modules/@grpc/grpc-js/src/call.ts:81:17)
    at Object.onReceiveStatus (/Users/haili/workspaces/lab/langchain-js/node_modules/.pnpm/@grpc+grpc-js@1.8.17/node_modules/@grpc/grpc-js/src/client.ts:356:55)
    at [/Users/haili/workspaces/lab/langchain-js/node_modules/.pnpm/](https://file+.vscode-resource.vscode-cdn.net/Users/haili/workspaces/lab/langchain-js/node_modules/.pnpm/)@grpc+grpc-js@1.8.17/node_modules/@grpc/grpc-js/src/call-interface.ts:149:27
    at Object.onReceiveStatus (/Users/haili/workspaces/lab/langchain-js/node_modules/.pnpm/@zilliz+milvus2-sdk-node@2.2.24/node_modules/@zilliz/milvus2-sdk-node/milvus/utils/Grpc.ts:184:23)
    at Object.onReceiveStatus (/Users/haili/workspaces/lab/langchain-js/node_modules/.pnpm/@grpc+grpc-js@1.8.17/node_modules/@grpc/grpc-js/src/client-interceptors.ts:455:34)
    at Object.onReceiveStatus (/Users/haili/workspaces/lab/langchain-js/node_modules/.pnpm/@grpc+grpc-js@1.8.17/node_modules/@grpc/grpc-js/src/client-interceptors.ts:417:48)
    at [/Users/haili/workspaces/lab/langchain-js/node_modules/.pnpm/](https://file+.vscode-resource.vscode-cdn.net/Users/haili/workspaces/lab/langchain-js/node_modules/.pnpm/)@grpc+grpc-js@1.8.17/node_modules/@grpc/grpc-js/src/resolving-call.ts:111:24
    at processTicksAndRejections (node:internal/process/task_queues:77:11)
for call at
 {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} }
}

@webup hi, I'm working well after replace the real token, address and openaikey.
But i'm face this error once, resolved it after open my vpn :)
ec87cb9d-8361-4675-be0e-92c069b7924b