-
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]: There are remaining segments that have not been merged compaction and GC #32765
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
ThreadDao
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 6, 2024
/assign |
@XuanYang-cn could be a bug injected by #32326, which was reverted in v2.4.1 |
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 6, 2024
The choosing of the same segments making datanode Lock Segment twice, and block forever.
|
XuanYang-cn
added a commit
to XuanYang-cn/milvus
that referenced
this issue
May 7, 2024
DataNode would stuck at compactor try to lock the same segmentID See also: milvus-io#32765 Signed-off-by: yangxuan <xuan.yang@zilliz.com>
sre-ci-robot
pushed a commit
that referenced
this issue
May 7, 2024
DataNode would stuck at compactor try to lock the same segmentID See also: #32765 --------- Signed-off-by: yangxuan <xuan.yang@zilliz.com>
XuanYang-cn
pushed a commit
to XuanYang-cn/milvus
that referenced
this issue
May 8, 2024
fix: Compaction trigger choose 2 same segments (milvus-io#32800) DataNode would stuck at compactor try to lock the same segmentID See milvus-io#32328, milvus-io#32765 Co-Authored-by: Ted Xu <ted.xu@zilliz.com> Signed-off-by: yangxuan <xuan.yang@zilliz.com>
XuanYang-cn
pushed a commit
to XuanYang-cn/milvus
that referenced
this issue
May 8, 2024
fix: Compaction trigger choose 2 same segments (milvus-io#32800) DataNode would stuck at compactor try to lock the same segmentID See milvus-io#32328, milvus-io#32765 Co-Authored-by: Ted Xu <ted.xu@zilliz.com> Signed-off-by: yangxuan <xuan.yang@zilliz.com>
@ThreadDao Please help verify master branch, THX |
/assign @ThreadDao |
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
Current Behavior
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
argo workflow: https://argo-workflows.zilliz.cc/archived-workflows/qa/62a9b6ae-64a6-4e73-83b3-397a2a8d2d8f?nodeId=zong-concurrent-upgrade-config-cron-1714402800-1423649165
pods:
Anything else?
No response
The text was updated successfully, but these errors were encountered: