[Bug]: @zilliz/milvus2-sdk-node Unable to connect milvus

[lcxyhhxi]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version:2.3.3
- "@zilliz/milvus2-sdk-node": "^2.4.9",

Current Behavior

import { MilvusClient } from "@zilliz/milvus2-sdk-node";

// Milvus 连接配置
const MILVUS_CONFIG = {
  address: 'localhost:19530',
};

console.log("MILVUS_CONFIG", MILVUS_CONFIG);

export const milvusClient = new MilvusClient(MILVUS_CONFIG);

8 |  * @param status
29 |  */
30 | function callErrorFromStatus(status, callerStack) {
31 |     const message = `${status.code} ${constants_1.Status[status.code]}: ${status.details}`;
32 |     const error = new Error(message);
                           ^
error: 4 DEADLINE_EXCEEDED: Deadline exceeded after 15.005s,name resolution: 0.011s,metadata filters: 0.002s,LB pick: 0.004s,remote_addr=127.0.0.1:19530
 code: "4"

      at callErrorFromStatus (/Users/licuan/DT/chat-gpt/node_modules/@grpc/grpc-js/build/src/call.js:32:23)
      at onReceiveStatus (/Users/licuan/DT/chat-gpt/node_modules/@grpc/grpc-js/build/src/client.js:278:36)
      at /Users/licuan/DT/chat-gpt/node_modules/@grpc/grpc-js/build/src/call-interface.js:78:35
      at onReceiveStatus (/Users/licuan/DT/chat-gpt/node_modules/@zilliz/milvus2-sdk-node/dist/milvus/utils/Grpc.js:148:25)
      at onReceiveStatus (/Users/licuan/DT/chat-gpt/node_modules/@grpc/grpc-js/build/src/call-interface.js:73:23)
      at onReceiveStatus (/Users/licuan/DT/chat-gpt/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:361:141)
      at onReceiveStatus (/Users/licuan/DT/chat-gpt/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:372:66)
      at /Users/licuan/DT/chat-gpt/node_modules/@grpc/grpc-js/build/src/resolving-call.js:177:17
      at makeUnaryRequest (/Users/licuan/DT/chat-gpt/node_modules/@grpc/grpc-js/build/src/client.js:231:13)
      at /Users/licuan/DT/chat-gpt/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19
      at /Users/licuan/DT/chat-gpt/node_modules/@zilliz/milvus2-sdk-node/dist/milvus/utils/Function.js:3:109
      at new Promise (1:11)
      at /Users/licuan/DT/chat-gpt/node_modules/@zilliz/milvus2-sdk-node/dist/milvus/utils/Function.js:3:20
      at fulfilled (/Users/licuan/DT/chat-gpt/node_modules/@zilliz/milvus2-sdk-node/dist/milvus/utils/Function.js:29:49)

Bun v1.1.21 (macOS arm64)

Expected Behavior

No response

Steps To Reproduce

Milvus Log

No response

Anything else?

No response

[dosubot]

@lcxyhhxi Hello there! I'm here to help you with any bugs, questions, or contributions. Let's work together to solve the issue you're facing.

The DEADLINE_EXCEEDED error in gRPC typically indicates that a request took longer than the allowed time to complete. Here are a few steps you can take to troubleshoot and potentially resolve this issue:

1. Check Milvus Server Status: Ensure that the Milvus server is running and accessible at localhost:19530. You can verify this by trying to connect using a different client or tool.

2. Network Configuration: Verify that there are no network or firewall settings blocking the connection to the Milvus server on port 19530.

3. Increase Timeout: If the server is running but the request is timing out, you might need to increase the timeout setting for gRPC calls. Unfortunately, I don't have specific information on how to adjust the timeout in the Milvus Node.js SDK, but you might find this setting in the SDK's configuration options or documentation.

4. Check SDK and Server Compatibility: Ensure that the versions of the Milvus server and the Node.js SDK are compatible. Sometimes, version mismatches can lead to unexpected errors.

5. Review Logs: Check the Milvus server logs for any errors or warnings that might provide more context about the connection issue.

These steps should help you identify and resolve the connection issue with Milvus using the Node.js SDK.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[yanliang567]

1. please double check the milvus is running healthy
2. please make sure the network is connective
3. if using another sdk, e.g. pymilvus, does it work?

/assign @lcxyhhxi
/unassign