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]: falled to query: node offline #32456

Closed
1 task done
rh01 opened this issue Apr 19, 2024 · 4 comments
Closed
1 task done

[Bug]: falled to query: node offline #32456

rh01 opened this issue Apr 19, 2024 · 4 comments
Assignees
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. stale indicates no udpates for 30 days

Comments

@rh01
Copy link

rh01 commented Apr 19, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.4.0-rc.1
- 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: 1000/1T
- GPU: 
- Others:

Current Behavior

The issue we are currently facing is that when deleting an empty search result, the deletion process gets stuck, causing problems with the cluster. As a result, the cluster is no longer able to perform queries properly in this collection.

MilvusException: <MilvusException: (code=503, message=failed to query: node offline[node=77]; node offline[node=77]; segment lacks[segment=448778450427470574]: channel not available[channel=milvus04-rootcoord-dml_1_448670693629703498v0])>

image

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

logs.tar.gz

Anything else?

No response

@rh01 rh01 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 Apr 19, 2024
@czs007 czs007 assigned aoiasd and unassigned yanliang567 Apr 19, 2024
@czs007
Copy link
Contributor

czs007 commented Apr 19, 2024

@rh01 we are investing it.

@xiaofan-luan
Copy link
Contributor

is there some logs about it?

@xiaofan-luan
Copy link
Contributor

might be something fixed already. I know several issue about segment allocaton

Copy link

stale bot commented May 19, 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 May 19, 2024
@stale stale bot closed this as completed Jun 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 needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. stale indicates no udpates for 30 days
Projects
None yet
Development

No branches or pull requests

5 participants