-
Notifications
You must be signed in to change notification settings - Fork 3k
Issues: milvus-io/milvus
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[Bug]: Scalar indexes cannot search out data
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: Latency spikes were observed when deleting 60% entities during concurrent searches
kind/bug
Issues or changes related a bug
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: Milvus embedding search with filtering does not work in the first 5-10 minutes
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: Zero Recall Rate, Very Strange for multi-vector search!!!!!!!
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: [benchmark][standalone] TimeTick Lag is very high, causing DQL request timeout
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: [benchmark][cluster] search RT almost doubled after enabling streamingNode
feature/streaming node
streaming node feature
kind/bug
Issues or changes related a bug
test/benchmark
benchmark test
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: insert data not run flush, data loss occurs after restarting querynode and datanode.
kind/bug
Issues or changes related a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: Queries intermittently failing
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: During the rolling upgrade process, the datanode experiences a sudden surge in memory usage, leading to OOM kills, and the querynode also continues to crash
kind/bug
Issues or changes related a bug
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: Unable to Build GPU Index on Milvus Cluster
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#38465
opened Dec 15, 2024 by
abdul3909
1 task done
[Bug]: HTTP V2 restful Return "code":0
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: [benchmark][cluster] hybrid_search raises error Issues or changes related a bug
test/benchmark
benchmark test
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
incomplete query result, missing id %!s(int64=0), len(searchIDs) = 100, len(queryIDs) = 99, collection=***: inconsistent requery result
in concurrent DML & DQL scene
kind/bug
[Bug]: [one pod standalone]when Milvus recovers from pod kill chaos, most of its interfaces are not available
kind/bug
Issues or changes related a bug
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: build index hang if trying to build scann index on a milvus running with simd sse4_2
kind/bug
Issues or changes related a bug
kind/feature
Issues related to feature request from users
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: MilvusException: <MilvusException: (code=1100, message=create index on 104 field is not supported: invalid parameter[expected=supported field][actual=create index on 104 field])>
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: Error Msg is meaningless
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: [CI] test_bulk_insert_all_field_with_numpy timeout due to slow stats task
ci/e2e
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: Milvus does not start if I setup minio seperately in the same namespace
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#38637
opened Dec 20, 2024 by
mananpreetsingh
1 task done
can not load collection[Bug]:
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: [benchmark][cluster] Create collection and create index raise error Issues or changes related a bug
test/benchmark
benchmark test
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
context deadline exceeded
in concurrent dql & ddl scene
kind/bug
[Bug]: Rest APIs not working with TLS enabled
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: After the pulsar pod failure is resolved, pulsar bookie still cannot recover
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: search/query/index's rto is about 30s during rolling update from v2.4.5 to 2.4-20240709-737bd7c7-amd64
kind/bug
Issues or changes related a bug
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
test/rolling upgrade
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: [benchmark][standalone] Each request RT gradually increases in concurrent DDL scene
2.4-features
kind/bug
Issues or changes related a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
test/benchmark
benchmark test
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: When performing a text match query in a growing segment, the result will be empty.
ci/e2e
feature/text match
kind/bug
Issues or changes related a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.