-
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]: After reinstalling Milvus, the QueryNode restarted during the testing process.
kind/bug
Issues or changes related a bug
test/chaos
chaos test
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Enhancement]: make management restful api idempotent
kind/enhancement
Issues or changes related to enhancement
#34985
opened Jul 25, 2024 by
weiliu1031
1 task done
[Bug]: Segment lack caused by deduplicate segment task
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#34781
opened Jul 18, 2024 by
weiliu1031
1 task done
[Enhancement]: Skip update collection next target if segment/channel list doesn't change
kind/enhancement
Issues or changes related to enhancement
#34715
opened Jul 16, 2024 by
weiliu1031
1 task done
[Enhancement]: Preserve fixed-size memory in delegator node for growing segment
kind/enhancement
Issues or changes related to enhancement
#34595
opened Jul 11, 2024 by
weiliu1031
1 task done
[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-update
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]: After executing "rollout restart", the insert/search/query service will experience service degradation.
kind/bug
Issues or changes related a bug
test/chaos
chaos test
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: Data distribution across multiple queryNode is not balanced
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]: 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]: Channels are not evenly balanced among dataNode
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: After transferring replicas to new query nodes, the segments still remain on the old query nodes.
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
[Bug]: [Nightly] Load collection will occasionally fail for timeout
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]: [one pod standalone] Flush failed: code=500, message=channel not found when recovered from pod kill
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]: [one pod standalone]when Milvus recovers from pod kill chaos, most of its interfaces are not available
2.4-features
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.
[Feature]: Add database level Resource Group/Replica
kind/feature
Issues related to feature request from users
#30040
opened Jan 16, 2024 by
xiaofan-luan
1 task done
[Feature]: Support more restful command for devops
kind/feature
Issues related to feature request from users
#29261
opened Dec 17, 2023 by
xiaofan-luan
1 task done
[Feature]: Support Graceful Shutdown of Worker Nodes in Milvus
kind/feature
Issues related to feature request from users
#24272
opened May 19, 2023 by
alexjst
1 task done
[Feature]: Semi Query mode
kind/feature
Issues related to feature request from users
#20290
opened Nov 3, 2022 by
jiaoew1991
1 task done
ProTip!
Find all open issues with in progress development work with linked:pr.