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
Current quotas can be either keyed or non-keyed. I'd like to be able to have both for the same user.
Say a ClickHouse is shared between 2 customer facing services, we can limit to some degree impact of a service by using per user (ClickHouse user) quotas. On the other side we can limit customers impact on the cluster by imposing limits using quotas and making the quota <keyed />.
I'd like to define both. Have a per-customer (quota key) quota and a global service quota (ClickHouse user).
The text was updated successfully, but these errors were encountered:
That will be useful. Although quotas mechanism is not under development right now. We hope that we can do major refactoring on quotas/events/limits, but please don't wait for it. Minor changes are welcome.
Current quotas can be either keyed or non-keyed. I'd like to be able to have both for the same user.
Say a ClickHouse is shared between 2 customer facing services, we can limit to some degree impact of a service by using per user (ClickHouse user) quotas. On the other side we can limit customers impact on the cluster by imposing limits using quotas and making the quota
<keyed />
.I'd like to define both. Have a per-customer (quota key) quota and a global service quota (ClickHouse user).
The text was updated successfully, but these errors were encountered: