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

[Bug]: ["fail to update resolver state"] [scheme=milvus-session] [id=17] [error="bad resolver state"] #39538

Open
1 task done
dt7-wcf opened this issue Jan 23, 2025 · 2 comments
Assignees
Labels
kind/bug Issues or changes related a bug triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@dt7-wcf
Copy link

dt7-wcf commented Jan 23, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:2.5.3
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

my console reported an error
[2025/01/23 03:46:07.763 +00:00] [WARN] [resolver/watch_based_grpc_resolver.go:55] ["fail to update resolver state"] [scheme=milvus-session] [id=17] [error="bad resolver state"]
2025-01-23T03:46:07.964112602Z [2025/01/23 03:46:07.963 +00:00] [WARN] [lazygrpc/conn.go:60] ["async dial failed, wait for retry..."] [error="context deadline exceeded"]
How to solve it

Expected Behavior

No response

Steps To Reproduce

Milvus Log

No response

Anything else?

No response

@dt7-wcf dt7-wcf added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 23, 2025
@yanliang567
Copy link
Contributor

@dt7-wcf could you please share more info about

  1. how to reproduce the issue? what did you do before meeting this issue?
  2. attach the full milvus logs for investigation. If you install Milvus with k8s, please refer this doc to export the whole Milvus logs.
    If you install Milvus with docker-compose, please use docker-compose logs > milvus.log to export the logs.

/assign @dt7-wcf
/unassign

@sre-ci-robot sre-ci-robot assigned dt7-wcf and unassigned yanliang567 Jan 24, 2025
@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 24, 2025
@xiaofan-luan
Copy link
Collaborator

you need to check the network, especially your dns.

it seems that there is a network access failure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants