[Bug]: Upsert failed: quota exceeded[reason=rate type: DMLUpsert] although the memory and tt delay are normal about milvus HOT 6 OPEN

• https://argo-workflows.zilliz.cc/archived-workflows/qa/17005b73-39aa-44be-8993-3ce24c3e72eb?nodeId=compact-opt-partitionkey-4d

from milvus.

/assign @aoiasd
I don't think we have enlable limit and quota in this case. but the quota exceeded error should not report
/unassign

from milvus.

using v2.4.1, we met the same issue

we found that, in the yaml of rootcoord in live env (as pic shows): quotaAndLimits.enabled: true

But in fact, we didn't configure this parameter, which by default should be false.

So we explicitly set

quotaAndLimits:
    enabled: false

and issue was gone

The issue leads to 2 tasks, IMO:

1. quotaAndLimits.enabled not in any docs, I found it in code. So related documents needs to be updated
2. Find out why quotaAndLimits.enabled becomes true without configured..

from milvus.

BTW, I don't think the attach PR is an actual fix, it doesn't solve the task 2 I mentioned

from milvus.

using v2.4.1, we met the same issue

we found that, in the yaml of rootcoord in live env (as pic shows): quotaAndLimits.enabled: true But in fact, we didn't configure this parameter, which by default should be false.

So we explicitly set

quotaAndLimits:
    enabled: false

and issue was gone

The issue leads to 2 tasks, IMO:

1. quotaAndLimits.enabled not in any docs, I found it in code. So related documents needs to be updated
2. Find out why quotaAndLimits.enabled becomes true without configured..

related code line:

from milvus.

waiting for verifying...

from milvus.