-
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]: wrong cp lag metrics #35588
Comments
/assign @XuanYang-cn |
/unassign |
Channel checkpoint meta lifecycle is buggy. Checkpoints are often left in the meta even if collections are dropped. And the creation and the deletion of the metrics are also in a chaos. Here're the rules I need to check:
|
do we need to hack channel cp meta to fix the problem for now? |
See also: milvus-io#35588 Signed-off-by: yangxuan <[email protected]>
See also: milvus-io#35588 pr: milvus-io#35658 Signed-off-by: yangxuan <[email protected]>
@xiaofan-luan I think so. I believe this is causing numerous false alarms, very annoying. see milvus-io/birdwatcher#303 |
See also: #35588 pr: #35658 --------- Signed-off-by: yangxuan <[email protected]>
See also: #35588 --------- Signed-off-by: yangxuan <[email protected]>
/assign @pingliu |
Is there an existing issue for this?
Environment
Current Behavior
Expected Behavior
No response
Steps To Reproduce
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: