-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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]: Query failed: Timestamp lag too large lag(129h36m35.55s) max(24h0m0s) #29619
Comments
it seems that the tt lag is huge in you milvus cluster @weiZhenkun Could you please refer this doc to export the whole Milvus logs for investigation? /assign @weiZhenkun |
/assign @congqixia /unassign @weiZhenkun |
Has the problem been solved? I had the same problem. |
There might be many different situation that could trigger this issue. |
I also meet this problem , version 2.3.4 or 2.4.1 ,detail logs below |
We will need more logs qfrom querynode and datanode to understand why this happens. |
Is there an existing issue for this?
Environment
Current Behavior
query error.
Expected Behavior
query error:
failed to search/query delegator 10 for channel demo-cluster3-rootcoord-dml_1_445021135592215568v0: fail to Search, QueryNode ID=10, reason=Timestamp lag too large lag(129h36m35.55s) max(24h0m0s): attempt #1: no available shard delegator found: service unavailable
Steps To Reproduce
Milvus Log
query error.
Anything else?
query error.
The text was updated successfully, but these errors were encountered: