[Bug]: fail to update resolver state

[venerate-young]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: v2.5.4
- Deployment mode(standalone or cluster): standalone
- MQ type(rocksmq, pulsar or kafka): default
- OS(Ubuntu or CentOS): docker

Current Behavior

After following the official tutorial (https://milvus.io/docs) to download Dockerfile and Milvus, the service consistently fails to start properly. The issue persists despite multiple debugging attempts using basic configurations and recommended solutions from documentation.

Expected Behavior

I hope it can work normally

Steps To Reproduce

docker compose -p milvus up

Milvus Log

2025-02-26 22:29:40 [2025/02/26 14:29:40.137 +00:00] [INFO] [sessionutil/session_util.go:513] ["Service registered successfully"] [ServerName=querynode] [serverID=1]
2025-02-26 22:29:40 [2025/02/26 14:29:40.137 +00:00] [INFO] [datacoord/server.go:953] ["received querynode register"] [address=172.18.0.4:21123] [serverID=1]
2025-02-26 22:29:40 [2025/02/26 14:29:40.137 +00:00] [INFO] [datacoord/index_engine_version_manager.go:71] ["addOrUpdate version"] [nodeId=1] [minimal=0] [current=6]
2025-02-26 22:29:40 [2025/02/26 14:29:40.138 +00:00] [INFO] [querycoordv2/server.go:778] ["add node to NodeManager"] [nodeID=1] [nodeAddr=172.18.0.4:21123]
2025-02-26 22:29:40 [2025/02/26 14:29:40.138 +00:00] [INFO] [components/query_node.go:63] ["QueryNode successfully started"]
2025-02-26 22:29:40 [2025/02/26 14:29:40.139 +00:00] [INFO] [task/scheduler.go:323] ["add executor for new QueryNode"] [nodeID=1]
2025-02-26 22:29:40 [2025/02/26 14:29:40.139 +00:00] [INFO] [dist/dist_handler.go:66] ["start dist handler"] [nodeID=1]
2025-02-26 22:29:40 [2025/02/26 14:29:40.140 +00:00] [INFO] [meta/resource_manager.go:855] ["transfer node to resource group"] [rgName=__default_resource_group] [originalRG=_] [node=1]
2025-02-26 22:29:40 [2025/02/26 14:29:40.140 +00:00] [INFO] [meta/resource_manager.go:472] ["HandleNodeUp: add node to resource group"] [rgName=__default_resource_group] [node=1] []
2025-02-26 22:29:40 [2025/02/26 14:29:40.224 +00:00] [INFO] [sessionutil/session_util.go:953] ["register session success"] [role=querynode] [key=by-dev/meta/session/querynode-1]
2025-02-26 22:29:40 [2025/02/26 14:29:40.369 +00:00] [WARN] [resolver/watch_based_grpc_resolver.go:55] ["fail to update resolver state"] [scheme=milvus-session] [id=5] [error="bad resolver state"]
2025-02-26 22:29:40 [2025/02/26 14:29:40.572 +00:00] [WARN] [lazygrpc/conn.go:60] ["async dial failed, wait for retry..."] [error="context deadline exceeded"]
2025-02-26 22:29:40 [2025/02/26 14:29:40.641 +00:00] [WARN] [dist/dist_handler.go:125] ["node last heart beat time lag too behind"] [now=2025/02/26 14:29:40.641 +00:00] [lastHeartBeatTime=1970/01/01 00:00:00.000 +00:00] [nodeID=1]
2025-02-26 22:29:40 [2025/02/26 14:29:40.641 +00:00] [INFO] [dist/dist_handler.go:114] ["pull and handle distribution done"] [respSize=13] [pullDur=802.333µs] [handleDur=58.917µs]
2025-02-26 22:29:42 [2025/02/26 14:29:42.490 +00:00] [WARN] [resolver/watch_based_grpc_resolver.go:55] ["fail to update resolver state"] [scheme=milvus-session] [id=6] [error="bad resolver state"]
2025-02-26 22:29:42 [2025/02/26 14:29:42.690 +00:00] [WARN] [lazygrpc/conn.go:60] ["async dial failed, wait for retry..."] [error="context deadline exceeded"]
2025-02-26 22:29:44 [2025/02/26 14:29:44.615 +00:00] [WARN] [resolver/watch_based_grpc_resolver.go:55] ["fail to update resolver state"] [scheme=milvus-session] [id=7] [error="bad resolver state"]
2025-02-26 22:29:44 [2025/02/26 14:29:44.820 +00:00] [WARN] [lazygrpc/conn.go:60] ["async dial failed, wait for retry..."] [error="context deadline exceeded"]
2025-02-26 22:29:50 [2025/02/26 14:29:50.235 +00:00] [WARN] [resolver/watch_based_grpc_resolver.go:55] ["fail to update resolver state"] [scheme=milvus-session] [id=8] [error="bad resolver state"]
2025-02-26 22:29:50 [2025/02/26 14:29:50.436 +00:00] [WARN] [lazygrpc/conn.go:60] ["async dial failed, wait for retry..."] [error="context deadline exceeded"]

Anything else?

milvus.yaml and docker-compose.yml

docker-milvus.zip

milovus.log

milvus.log

[dosubot]

Hey @venerate-young! 👋 I'm here to help you out with any bugs, questions, or contributions you may have.

To resolve the "fail to update resolver state" error in Milvus when using Docker in standalone mode, you should modify the etcd configuration in your docker-compose.yml file. Specifically, change the -advertise-client-urls parameter from 'http://127.0.0.1:2379' to 'http://etcd:2379'. This adjustment is necessary because the etcd connection cannot be established with the default localhost configuration in a containerized environment ^[1].

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}

[venerate-young]

-advertise-client-urls

Hey @venerate-young! 👋 I'm here to help you out with any bugs, questions, or contributions you may have.

To resolve the "fail to update resolver state" error in Milvus when using Docker in standalone mode, you should modify the etcd configuration in your docker-compose.yml file. Specifically, change the -advertise-client-urls parameter from 'http://127.0.0.1:2379' to 'http://etcd:2379'. This adjustment is necessary because the etcd connection cannot be established with the default localhost configuration in a containerized environment [1].

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

I am sure I have modified

  standalone:
    container_name: milvus-standalone
    image: milvusdb/milvus:v2.5.4
    command: [ "milvus", "run", "standalone" ]
    security_opt:
      - seccomp:unconfined
    environment:
      ETCD_ENDPOINTS: etcd:2379
      MINIO_ADDRESS: minio:9000
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/milvus:/var/lib/milvus
      - ./milvus.yaml:/milvus/configs/milvus.yaml
    healthcheck:
      test: [ "CMD", "curl", "-f", "http://localhost:9091/healthz" ]
      interval: 30s
      start_period: 90s
      timeout: 20s
      retries: 3
    ports:
      - "19530:19530"
      - "9091:9091"
    depends_on:
      - "etcd"
      - "minio"

etcd:
  # Endpoints used to access etcd service. You can change this parameter as the endpoints of your own etcd cluster.
  # Environment variable: ETCD_ENDPOINTS
  # etcd preferentially acquires valid address from environment variable ETCD_ENDPOINTS when Milvus is started.
  endpoints: etcd:2379