What are the load balancing algorithms supported for the stateless brokers? #506
Replies: 1 comment
-
|
None at present. However, there is work in progress on authentication (#47) that could enable throttling of clients, and routing of requests depending on a QOS (with accompanying ACL/config). There is also a tansu proxy that could be used to route/layer requests: Lines 174 to 200 in ad005c6 it currently adapts metadata/find_coordinator responses, but could provide routing instead (requests for topic A all go to broker B). As all storage/metadata is delegated to PostgreSQL/S3/SQLite/..., it could be used to route client A to SQLite, B to PostgreSQL/etc. One of the original concepts, was having lots of "small" single broker ephemeral clusters rather than having a single "big" cluster with all the issues of noisy neighbours/etc. I am also looking at slatedb (#500) for read heavy topics on S3 that might benefit from a layer of caching. Happy to discuss in more detail if you have particular questions. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Does Tansu support load balancing based on consistent hashing or balancing the incoming connections? What are the options supported and does system do anything to detect and balance hot partitions or to evenly spread the load of overpartitioned topics / large number of topics with a highly skewed load?
Beta Was this translation helpful? Give feedback.
All reactions