You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you can probably using https://milvus.io/docs/resource_group.md to isolate resource.
Each DB can be specified to one resource group with several pods so they can be limited
Do I understand correctly that the amount of RAM (and other resources) cannot be set directly for the ResourceGroup and the minimum amount of allocated resource will be one QueryNode? That is, I can create many small QueryNodes in Kubernetes and allocate resources for groups as a number of QueryNodes?
Unfortunately, I did not find a link between ResourceGroups in Databases, only for Collections. I have RBAC configured for the teams at the Database level. Is it possible to allocate ResourceGroups for databases?
Do I understand correctly that the amount of RAM (and other resources) cannot be set directly for the ResourceGroup and the minimum amount of allocated resource will be one QueryNode? That is, I can create many small QueryNodes in Kubernetes and allocate resources for groups as a number of QueryNodes?
Unfortunately, I did not find a link between ResourceGroups in Databases, only for Collections. I have RBAC configured for the teams at the Database level. Is it possible to allocate ResourceGroups for databases?
yes you could. you can bind a databse with a group of querynodes
Is there an existing issue for this?
Is your feature request related to a problem? Please describe.
I'm looking for a way to limit memory usage for databases. Right now I have multiple teams fighting for query node memory.
Describe the solution you'd like.
Database memory limit option
Describe an alternate solution.
No response
Anything else? (Additional Context)
Perhaps there is an alternative way to limit the use of operational memory for databases. Please advise. Maybe I should use the option https://milvus.io/docs/configure_quotaandlimits.md#quotaAndLimitslimitWritingdiskProtectiondiskQuotaPerDB ?
The text was updated successfully, but these errors were encountered: