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

load balancing: slow coordinator avoidance #81

Closed
kbr- opened this issue Jun 30, 2021 · 2 comments
Closed

load balancing: slow coordinator avoidance #81

kbr- opened this issue Jun 30, 2021 · 2 comments

Comments

@kbr-
Copy link

kbr- commented Jun 30, 2021

It would be nice to have a real load balancing strategy which chooses coordinators based on actual metrics such as how fast it can process requests.

See scylladb/scylladb#5715 for motivation. I explain in the comments what the issue is (it is a driver-side issue).

The 4.x versions of the Java driver AFAIK do have such strategies - at least one.
From https://docs.datastax.com/en/developer/java-driver/4.11/manual/core/load_balancing/#built-in-policies:

DefaultLoadBalancingPolicy should almost always be used; it requires a local datacenter to be specified either programmatically when creating the session, or via the configuration (see below). It can also use a highly efficient slow replica avoidance mechanism, which is by default enabled.

@martin-sucha
Copy link

FYI, we have something like this in our fork of gocql https://github.com/kiwicom/gocql/blob/master/tokenawarelatency.go (but it is a bit different to the java policy linked above).

@sylwiaszunejko
Copy link
Collaborator

Done in #168

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

No branches or pull requests

3 participants