Open ThreadDao opened 4 months ago
/assign @congqixia
Previous test result:
the target failed to sync and cause growing segment stuck in delegator. Digging why target update failed
Previous test result:
argo: https://argo-workflows.zilliz.cc/archived-workflows/qa/8c535d6e-68ea-4dc3-ac49-13772107181f?nodeId=level-zero-stable-1720105200-try-2485191624 image: 2.4-20240705-261b61e8 metrics of level-zero-insert-op-40-4759
/assign @bigsheeper Let's add a seal policy to keep growing segment of each shard to be less than 4GB
/assign @ThreadDao should be fixed, please help to verify
/unassign
Is there an existing issue for this?
Environment
Current Behavior
deploy milvus
deploy
level-zero-insert-op-96-4610
with 4 queryNodestest
results
queryNode (one of delegator oomkilled) metrics of level-zero-insert-op-96-4610
Expected Behavior
No response
Steps To Reproduce
Milvus Log
pods:
Anything else?
No response