Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[store] resource quota and isolation #1127

Closed
BohuTANG opened this issue Jul 21, 2021 · 3 comments
Closed

[store] resource quota and isolation #1127

BohuTANG opened this issue Jul 21, 2021 · 3 comments
Labels
C-improvement Category: improvement

Comments

@BohuTANG
Copy link
Member

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.

@BohuTANG BohuTANG added the C-improvement Category: improvement label Jul 21, 2021
@BohuTANG BohuTANG added this to the v0.5 milestone Jul 21, 2021
@BohuTANG BohuTANG mentioned this issue Jul 21, 2021
23 tasks
@drmingdrmer
Copy link
Member

Quote:

  • 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.

@BohuTANG
Copy link
Member Author

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.

@BohuTANG
Copy link
Member Author

The store is lift to compute node, closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-improvement Category: improvement
Projects
None yet
Development

No branches or pull requests

2 participants