-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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]: milvus standalone crash by bitset assert check fail
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]: [benchmark] Continuous upsert and count(*), count(*) results are incorrect, and milvus panic
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]: After restarting, the number of search results is one less than the limit value.
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.
[Bug]: QueryNode oomkilled due to sudden increase in the number of growing segments
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]: one pod standalone restarted during test after chaos
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.
[Bug]: After a standalone rolling upgrade, memory usage surged to twice its original amount, resulting in an out-of-memory (OOM) error.
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.
[Bug]: Standalone oomkilled after upgrading mater branch image
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]: The results returned by the count(*) are inaccurate and keep changing
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]: Five out of seven flush requests 120s timeout
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]: [laion-1b] The count(*) result is more than expected after concurrently upserting data
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.
[Bug]: Flush timeout and search fails for nearly 17 minutes after chaos recovery from pod-kill standalone
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]: [laion-1b] The queryNode SIGABRT: abort with log: 'milvus::SegcoreError' what(): Error:RemoveDir:Directory not empty
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.
[Bug]: [GoSDK] Insert rows data with varchar field gets error: param column varchar has type string but collection field definition is string
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]: There are still thousands of small segments here but the compaction has stopped
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]: Query and ouput count(*) field hangs
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]: Search failed with error: Collection not fully loaded
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]: The milvus instance does not have any requests but the query count(*) results become larger
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]: [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]: Count(*) result decreases after reloading collection
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]: [benchmark][standalone] Collection load failed after rebuild index
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]: [benchmark][cluster] proxy mem usage increased abnormally and did not decrease after the test, client load raises error 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.
collection not loaded
2.4-features
kind/bug
[Bug]: [laion1b-test] The dropped collection has never been GC
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]: [bulk insert v2]In the "list import job" interface, the dbName parameter is not taking effect. Regardless of the different values set, the results returned are the same
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.
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]: count result of query less than expect with Mmap enabled
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]: [benchmark][cluster] flush 180s timeout in DQL scene with 1024 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.
reqs
for hybrid_search
2.4-features
kind/bug
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.