-
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]: Data Coord constantly tries to DescribeIndex on collections without index #33102
Closed
1 task done
Labels
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Comments
zhengbuqian
added
kind/bug
Issues or changes related a bug
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
May 16, 2024
/assign @xiaocai2333 |
yanliang567
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
May 16, 2024
Milvus will regularly count index information metrics. This is only counting metrics and will not affect the system. |
I will reduce the frequency of logs describing indexing failures. |
sre-ci-robot
pushed a commit
that referenced
this issue
May 21, 2024
…33212) issue: #33001 #33102 Signed-off-by: Cai Zhang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Is there an existing issue for this?
Environment
- Milvus version: master
Current Behavior
I created a collection and inserted some data. I didn't create any index on that, and from the logs I see lots of repeated
DescribeIndex
RPC failure. It kept being failed and retried and never stop.Expected Behavior
we should not try to
DescribeIndex
on collections without index, or at least it should not be infinite retried.Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: