-
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
[Enhancement]: Trigger compaction by size #32328
Labels
Comments
sre-ci-robot
pushed a commit
that referenced
this issue
Apr 23, 2024
See #32328 --------- Signed-off-by: Ted Xu <ted.xu@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>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is there an existing issue for this?
What would you like to be added?
I would like to change the compaction trigger size based, instead of estimation based.
Why is this needed?
Compaction is currently triggered by size estimated indirectly from row number, instead of segment size itself.
That kind of estimation is not accurate, especially in those cases that variable length columns are involved. If there is an underestimate, the actual size of the compact segment may exceed expectation and will never be fixed.
Anything else?
No response
The text was updated successfully, but these errors were encountered: