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
A centralized fast storage service for collecting user access statistics.
An algorithm to allocate resource evenly to every store-node, with the consideration of unevenly distributed user access.
A throttle component on every store node.
A user-friendly response design.
Isolation:
If fuse store is only used by fuse-query, this can be done by a query node, with the information provided by store that what store-node a user is bound to.
Otherwise, store need to provide a redirect response, to inform a client to access other store node.
But for untrusted client, I am not sure if this strategy will work as expected.
The quota(call throttle is more better) is to prevent some special users slow down the store, for example, select * from tb1.
Isolation can be thought later.
Summary
Because the store is multi-tenant with different levels of users requesting on it, we need to do some quota and isolation for the resource.
The text was updated successfully, but these errors were encountered: