[Bug]: The deleteBufferSizeProtection returns misleading error when triggering a force deny: memory quota exceeded

[ThreadDao]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

- Milvus version: 2.4-20241029-3d1e81fb-amd64
- Deployment mode(standalone or cluster): 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

server config

compact-opt-rate-100m-1/config/quotaandlimits.limitwriting.deleteBufferSizeProtection.enabled
true
compact-opt-rate-100m-1/config/quotaandlimits.limitwriting.deleteBufferSizeProtection.highWaterLevel
209715200
compact-opt-rate-100m-1/config/quotaandlimits.limitwriting.deleteBufferSizeProtection.lowWaterLevel
52428800

test

delete by pk in, gets an error

[2024-10-29 19:08:42,896 - INFO - ci_test]: delete (insert count: 0, delete count: 3000, upsert count: 0, timestamp: 0, success count: 0, err count: 0 cost 10.46596908569336s (tmp.py:103)
[2024-10-29 19:08:42,897 - INFO - ci_test]: start to delete with expr 3000 (tmp.py:98)
RPC error: [delete], <MilvusException: (code=9, message=quota exceeded[reason=memory quota exceeded, please allocate more resources])>, <Time:{'RPC start': '2024-10-29 19:08:42.898368', 'RPC error': '2024-10-29 19:08:44.406385'}>
Traceback (most recent call last):

Actually, the force deny reason is deleteBufferSize not memory

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

• loki logs

Anything else?

No response

[yanliang567]

/unassign