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]: proxy warning log ["status is nil, please fix it"] for query node #34171

Closed
1 task done
hwc1824 opened this issue Jun 25, 2024 · 4 comments
Closed
1 task done
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@hwc1824
Copy link

hwc1824 commented Jun 25, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

Though searching on collections, loading / releasing collection are working fine, all the proxy pod showed this warning message repeatedly, I tried to rolling restart the proxy and querynode but it didn't get resolved.

[2024/06/25 09:53:36.428 +00:00] [WARN] [grpcclient/client.go:520] ["status is nil, please fix it"] [traceID=81b39ecc6873a390a9c849cbdfd0efb2] [client_role=querynode-323] 
[stack="github.com/milvus-io/milvus/internal/util/grpcclient.(*ClientBase[...]).call.func2
	/go/src/github.com/milvus-io/milvus/internal/util/grpcclient/client.go:520
github.com/milvus-io/milvus/pkg/util/retry.Handle
	/go/src/github.com/milvus-io/milvus/pkg/util/retry/retry.go:104
github.com/milvus-io/milvus/internal/util/grpcclient.(*ClientBase[...]).call
	/go/src/github.com/milvus-io/milvus/internal/util/grpcclient/client.go:467
github.com/milvus-io/milvus/internal/util/grpcclient.(*ClientBase[...]).Call
	/go/src/github.com/milvus-io/milvus/internal/util/grpcclient/client.go:554
github.com/milvus-io/milvus/internal/util/grpcclient.(*ClientBase[...]).ReCall
	/go/src/github.com/milvus-io/milvus/internal/util/grpcclient/client.go:570
github.com/milvus-io/milvus/internal/distributed/querynode/client.wrapGrpcCall[...]
	/go/src/github.com/milvus-io/milvus/internal/distributed/querynode/client/client.go:90
github.com/milvus-io/milvus/internal/distributed/querynode/client.(*Client).Search
	/go/src/github.com/milvus-io/milvus/internal/distributed/querynode/client/client.go:202
github.com/milvus-io/milvus/internal/proxy.(*searchTask).searchShard
	/go/src/github.com/milvus-io/milvus/internal/proxy/task_search.go:685
github.com/milvus-io/milvus/internal/proxy.(*LBPolicyImpl).ExecuteWithRetry.func1
	/go/src/github.com/milvus-io/milvus/internal/proxy/lb_policy.go:180
github.com/milvus-io/milvus/pkg/util/retry.Do
	/go/src/github.com/milvus-io/milvus/pkg/util/retry/retry.go:44
github.com/milvus-io/milvus/internal/proxy.(*LBPolicyImpl).ExecuteWithRetry
	/go/src/github.com/milvus-io/milvus/internal/proxy/lb_policy.go:154
github.com/milvus-io/milvus/internal/proxy.(*LBPolicyImpl).Execute.func2
	/go/src/github.com/milvus-io/milvus/internal/proxy/lb_policy.go:218
golang.org/x/sync/errgroup.(*Group).Go.func1
	/go/pkg/mod/golang.org/x/sync@v0.5.0/errgroup/errgroup.go:75"]

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

I didn't found the similar warning message when I lower the milvus version to v2.4.0

@hwc1824 hwc1824 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 Jun 25, 2024
@xiaofan-luan
Copy link
Contributor

/assign @weiliu1031

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 26, 2024
@xiaofan-luan
Copy link
Contributor

/assign @aoiasd

@smellthemoon
Copy link
Contributor

may related with #34100

Copy link

stale bot commented Jul 27, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Jul 27, 2024
@stale stale bot closed this as completed Aug 7, 2024
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 stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

6 participants