-
Notifications
You must be signed in to change notification settings - Fork 3k
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]: Index failed during rolling upgrade #38741
Comments
/assign @weiliu1031 |
@zhuwenxing |
The index was eventually created successfully, but two issues were identified:
|
build index becomes slower, which is a know impact by stat task. won't fix |
please refine the timeout for building index if necessary |
/assign @zhuwenxing |
/assign @xiaocai2333 |
During an upgrade, existing segments will trigger stats tasks after the upgrade. This might lead to longer indexing times for newly triggered tasks, as the stats tasks generated by the the existing segments need to be processed first. |
will increase index timeout to 360s to for verifing |
still failed with 360s timeout for index artifacts-kafka-mixcoord-5808-server-logs.tar.gz cluster: 4am
|
According to the logs, when the index was previously set to 120s, there were 3 failures. Now with it set to 360s, there is one failure. This suggests that during the rolling upgrade, there appears to be a time window of approximately 360 seconds during which new indexes cannot be created. |
The CPU utilization of indexnode is relative low. After the PR #39084 is merged, indexnode can concurrently execute small index tasks and stats tasks, improving resource utilization. |
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/rolling_update_for_operator_test_simple/detail/rolling_update_for_operator_test_simple/5688/pipeline
log:
artifacts-kafka-mixcoord-5688-server-logs.tar.gz
Anything else?
No response
The text was updated successfully, but these errors were encountered: