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

Support distributing read queries over multiple servers #1984

Closed
kostko opened this issue Aug 8, 2019 · 1 comment
Closed

Support distributing read queries over multiple servers #1984

kostko opened this issue Aug 8, 2019 · 1 comment
Labels
c:ops Category: operations c:performance Category: performance c:storage Category: storage

Comments

@kostko
Copy link
Member

kostko commented Aug 8, 2019

Since storage nodes will need to answer a lot of read-only queries from clients, it would make sense to support an architecture where a single "storage worker" is actually internally composed of many servers that can distribute the read load.

The major difference to syncing with other untrusted servers is that we can assume that all servers within such a cluster are trusted and speed up syncing (e.g., by using Badger's replication mechanisms).

cc @ravenac95 @ptrus

@kostko kostko added c:storage Category: storage c:ops Category: operations c:performance Category: performance labels Aug 8, 2019
@kostko
Copy link
Member Author

kostko commented Aug 16, 2019

We should also consider easily supporting configurations that have tiered access with split nodes handling workloads for different classes of users:

  • Read/write storage access for (staked) committee members. Staked members in the current committees would always have unlimited access as this is needed for normal operation of the network and things like the availability probes.
  • Read storage access for random users. These could have much stricter usage limits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:ops Category: operations c:performance Category: performance c:storage Category: storage
Projects
None yet
Development

No branches or pull requests

1 participant