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]: failed to search/query delegator 13 for channel by-dev-rootcoord-dml_10_450726761228907207v0: fail to Search, QueryNode ID=13, reason=Timestamp lag too large #34320

Closed
1 task done
iwanglei1 opened this issue Jul 2, 2024 · 3 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

@iwanglei1
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: v2.3.4
- Deployment mode(standalone or cluster): standalone 
- MQ type(rocksmq, pulsar or kafka): Unknown 
- SDK version(e.g. pymilvus v2.0.0rc2): Attu v2.4.3
- OS(Ubuntu or CentOS): Ubuntu 22.04
- CPU/Memory: 80 core/ 256 G
- GPU: 4 * 3090
- Others:

Current Behavior

This error may be prompted during query. Setting data consistency can avoid the error, but the data cannot be queried.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@iwanglei1 iwanglei1 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 Jul 2, 2024
@yanliang567
Copy link
Contributor

usually it is about that datanode is not able to handle so many writing to milvus, but we need the completed logs to tell what was hanppending. Could you please refer this doc to export the whole Milvus logs for investigation?
For Milvus installed with docker-compose, you can use docker-compose logs > milvus.log to export the logs.

/assign @iwanglei1
/unassign

@sre-ci-robot sre-ci-robot assigned iwanglei1 and unassigned yanliang567 Jul 2, 2024
@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 Jul 2, 2024
@yanliang567
Copy link
Contributor

also please try to upgrade to milvus 2.3.18 or 2.4.5, which has fixed many issues in writing.

Copy link

stale bot commented Aug 4, 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 Aug 4, 2024
@stale stale bot closed this as completed Aug 11, 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

2 participants