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]: 所有的表都查不到数据 #28790

Closed
1 task done
suchenghui opened this issue Nov 28, 2023 · 4 comments
Closed
1 task done

[Bug]: 所有的表都查不到数据 #28790

suchenghui opened this issue Nov 28, 2023 · 4 comments
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@suchenghui
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

所有的表都查不到数据
,报错日志如下:
attempt #0: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #1: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #2: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #3: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #4: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #5: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #6: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: context done during sleep after run#6: context deadline exceeded: fail to search on all shard leaders

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

报错日志如下:
attempt #0: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #1: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #2: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #3: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #4: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #5: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: attempt #6: fail to get shard leaders from QueryCoord: segment=444255720359958542: segment lacks: channel=by-dev-rootcoord-dml_3_444255720359958467v0: channel not available: context done during sleep after run#6: context deadline exceeded: fail to search on all shard leaders

Anything else?

No response

@suchenghui suchenghui 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 Nov 28, 2023
Copy link
Contributor

The title and description of this issue contains Chinese. Please use English to describe your issue.

@xiaofan-luan
Copy link
Contributor

seems that all the channel can not be loaded.
please offer full logs with export_log.sh so we can know the detailed reason

@yanliang567
Copy link
Contributor

/assign @suchenghui
/unassign

@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 Nov 29, 2023
Copy link

stale bot commented Dec 29, 2023

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 Dec 29, 2023
@stale stale bot closed this as completed Jan 5, 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/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