Skip to content
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]: Forgetting to set blob memory size when compaction resulted a huge segment being generated #33280

Closed
1 task done
xiaocai2333 opened this issue May 22, 2024 · 3 comments
Assignees
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

@xiaocai2333
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:master
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Forgetting to set blob memory size when compaction resulted a huge segment being generated.

the segment max size config size is 1024M, but generated the segment with num rows is 3080000, and the dim is 768.
from the birdwatcher, all the segment after compaction, the memory size is 0.

Expected Behavior

should be set blob memory size in

return &Blob{
Key: strconv.Itoa(int(bsw.fieldSchema.FieldID)),
Value: b.Bytes(),
RowNum: int64(bsw.rw.numRows),
}, nil

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@xiaocai2333 xiaocai2333 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 22, 2024
@xiaocai2333
Copy link
Contributor Author

/assign @tedxu
/unassign @yanliang567

@sre-ci-robot sre-ci-robot assigned tedxu and unassigned yanliang567 May 22, 2024
@yanliang567 yanliang567 removed their assignment May 23, 2024
@yanliang567 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 23, 2024
@yanliang567 yanliang567 added this to the 2.4.2 milestone May 23, 2024
sre-ci-robot pushed a commit that referenced this issue May 24, 2024
See: #33280

Signed-off-by: Ted Xu <ted.xu@zilliz.com>
@yanliang567 yanliang567 modified the milestones: 2.4.2, 2.4.3 May 24, 2024
@xiaocai2333
Copy link
Contributor Author

fixed
/close

@sre-ci-robot
Copy link
Contributor

@xiaocai2333: Closing this issue.

In response to this:

fixed
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

XuanYang-cn pushed a commit to XuanYang-cn/milvus that referenced this issue Jun 24, 2024
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.
Projects
None yet
Development

No branches or pull requests

4 participants