-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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]: [benchmark][cluster] The number of growing segments on queryNode gradually increases, the amount of data loaded on queryNode is greater than data actually inserted #40382
Comments
I found a similar open issue regarding discrepancies in the number of segments and data loaded on the queryNode in Milvus. The issue is titled "[Bug]: count(*) returns a result that exceeds the actual number" and is currently open, but no solution has been found in the comments [1]. Regarding the increase in growing segments, Milvus manages growing and sealed segments using a For the transition from growing to sealed segments, Milvus uses an "autoHandoff" feature. This transition is triggered when a growing segment reaches a predefined threshold, at which point the segment is sealed, and index building begins. If To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
/assign @wangting0128 |
Is there an existing issue for this?
Environment
Current Behavior
argo task: bitmap-corn-1741143600
server:
Collection shard=16
queryNode - Segment Loaded Num
prepare 5 million data, concurrent insert 146 * 10 = 1460, delete 153 * 10 = 1530
queryNode - Queryable Entity Num
The amount of data has more than doubled
Expected Behavior
Same case, different image, tested normally
argo task: bitmap-corn-1741057200
image: 2.5-20250303-29c23545-amd64
server:
Steps To Reproduce
Milvus Log
No response
Anything else?
test result:
The text was updated successfully, but these errors were encountered: