-
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]: [one pod standalone]when Milvus recovers from pod kill chaos, most of its interfaces are not available #30314
Comments
/assign @LoveEachDay PTAL |
database space exceeded |
the error message has changed in master-20240305-3c9ffded
|
We'd change the default etcd settings for embedding mode.
|
still reproduced |
@LoveEachDay We'd change the auto compaction config for embed etcd which will mitigate the |
Fix #30314 Signed-off-by: Edward Zeng <jie.zeng@zilliz.com>
the but failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-cron/detail/chaos-test-cron/13356/pipeline |
/assign @weiliu1031 |
/assign |
/unassign @LoveEachDay @XuanYang-cn @weiliu1031 |
still reproduced in |
/assign @XuanYang-cn |
still reproduced in master-20250106-f0cddfd1-amd64 log: pod info
|
Is there an existing issue for this?
Environment
Current Behavior
collection not loaded
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/10981/pipeline
log:
artifacts-one-pod-standalone-pod-kill-10981-server-logs.tar.gz
Anything else?
No response
The text was updated successfully, but these errors were encountered: