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]: Import segemnt with row 0 and can never be cleaned #33604

Open
1 task done
bigsheeper opened this issue Jun 4, 2024 · 2 comments
Open
1 task done

[Bug]: Import segemnt with row 0 and can never be cleaned #33604

bigsheeper opened this issue Jun 4, 2024 · 2 comments
Assignees
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@bigsheeper
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: master & 2.4
- 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

img_v3_02bh_60d9a23d-c354-4c13-8cf1-af136a8a160g

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@bigsheeper bigsheeper 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 Jun 4, 2024
@bigsheeper bigsheeper self-assigned this Jun 4, 2024
sre-ci-robot pushed a commit that referenced this issue Jun 5, 2024
The data coordinator computed the appropriate number of import segments,
thus when importing in the data node, one can randomly select a segment.

issue: #33604

---------

Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
@bigsheeper
Copy link
Contributor Author

before:
22OsIOOTZ3
after:
8RIkMlgpJB

bigsheeper added a commit to bigsheeper/milvus that referenced this issue Jun 5, 2024
The data coordinator computed the appropriate number of import segments,
thus when importing in the data node, one can randomly select a segment.

issue: milvus-io#33604

---------

Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
sre-ci-robot pushed a commit that referenced this issue Jun 5, 2024
The data coordinator computed the appropriate number of import segments,
thus when importing in the data node, one can randomly select a segment.

issue: #33604

pr: #33605

Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
@xiaofan-luan
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: master & 2.4
- 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

img_v3_02bh_60d9a23d-c354-4c13-8cf1-af136a8a160g

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

I think this pr's name and description need to be improved. The generated segemnt with row 0 can never be cleaned and this is a critical bug

@bigsheeper bigsheeper changed the title [Bug]: The size of the import segments is uneven [Bug]: Import segemnt with row 0 and can never be cleaned Jun 20, 2024
yellow-shine pushed a commit to yellow-shine/milvus that referenced this issue Jul 2, 2024
The data coordinator computed the appropriate number of import segments,
thus when importing in the data node, one can randomly select a segment.

issue: milvus-io#33604

---------

Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
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 needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants