-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Open
Labels
kind/bugIssues or changes related a bugIssues or changes related a bugtriage/needs-informationIndicates an issue needs more information in order to work on it.Indicates an issue needs more information in order to work on it.
Milestone
Description
Is there an existing issue for this?
- I have searched the existing issues
Environment
- Milvus version:2.6.8
- Deployment mode(standalone or cluster):cluster
- MQ type(rocksmq, pulsar or kafka):
- SDK version(e.g. pymilvus v2.0.0rc2):2.6.5
- OS(Ubuntu or CentOS): CentOS
- CPU/Memory:
- GPU:
- Others:Current Behavior
There's a 10-second scheduled task upserting data to Mulvus. The total number of upserts within those 10 seconds is approximately 10,000, in batches of 2,000. Data is being written normally, but the streaming memory usage keeps increasing, and the segments show no data. I've tried manually flushing, but it didn't work.
Expected Behavior
No response
Steps To Reproduce
Milvus Log
No response
Anything else?
No response
Metadata
Metadata
Labels
kind/bugIssues or changes related a bugIssues or changes related a bugtriage/needs-informationIndicates an issue needs more information in order to work on it.Indicates an issue needs more information in order to work on it.