-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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]: flush timeout after milvus recovered from pulsar pod kill chaos test #34255
Comments
/assign @weiliu1031 |
/assign @bigsheeper |
segment after DN recovering and seek to 17:31:42, the msg in between 17:31:42 are lost cpTime=2024/06/27 17:46:30.521 are lost. so the flush is timeout.
|
Yes, after the datanode restart, the flowgraph did not receive insert data of segment 450758977781515919. There are several possible reasons for this:
|
it is not a stable reproduced issue. so it is a bit hard to verify and reproduce |
Try to add some key logs; we'll look into it if it happens again. |
There is a reproduced case in log:
|
reproduced in |
When the main dispatcher has not yet consumed data, curTs is 0. During this time, merging dispatchers should not be allowed; otherwise, the data of the solo dispatcher will be skipped. issue: #34255 --------- Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
/assign @zhuwenxing |
/unassign |
When the main dispatcher has not yet consumed data, curTs is 0. During this time, merging dispatchers should not be allowed; otherwise, the data of the solo dispatcher will be skipped. issue: milvus-io#34255 --------- Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
When the main dispatcher has not yet consumed data, curTs is 0. During this time, merging dispatchers should not be allowed; otherwise, the data of the solo dispatcher will be skipped. issue: milvus-io#34255 --------- Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
…us-io#34563) When the main dispatcher has not yet consumed data, curTs is 0. During this time, merging dispatchers should not be allowed; otherwise, the data of the solo dispatcher will be skipped. issue: milvus-io#34255 pr: milvus-io#34562 --------- Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
…us-io#34563) When the main dispatcher has not yet consumed data, curTs is 0. During this time, merging dispatchers should not be allowed; otherwise, the data of the solo dispatcher will be skipped. issue: milvus-io#34255 pr: milvus-io#34562 --------- Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
verified and not reproduced in |
Is there an existing issue for this?
Environment
Current Behavior
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-cron/detail/chaos-test-cron/15599/pipeline
log:
artifacts-pulsar-pod-kill-15599-server-logs.tar.gz
Anything else?
No response
The text was updated successfully, but these errors were encountered: