Skip to content

Add load balancing assertion to the stress test #268

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

Merged
merged 5 commits into from
Jul 14, 2017

Conversation

lutovich
Copy link
Contributor

Based on #267

lutovich added 3 commits July 11, 2017 18:14
It will now track count of active (checked out of the pool) resources
per key. Where key is a server address in the driver. Counter is
incremented when resource is acquired from the pool and decremented
when resource is released back to the pool.

Also added JSDocs in the `Pool` class.
This replaces the existing round-robin. It gives us better performance
with clusters composed of different machine capacities.
Lease connected load balancing strategy selects start index in
round-robin fashion to avoid always selecting same machine when cluster
does not have any running transactions or all machines have same number
of active connections.

It is possible to go back to previous round-robin load balancing
strategy using an experimental config setting:
```
  {loadBalancingStrategy: 'round_robin'}
```
@lutovich lutovich force-pushed the 1.5-check-lb-in-stress-test branch from 26781c5 to 5cfe197 Compare July 11, 2017 22:03
lutovich added 2 commits July 13, 2017 12:27
To make sure both followers and read replicas serve similar
amount of read queries.
@lutovich lutovich force-pushed the 1.5-check-lb-in-stress-test branch from 5cfe197 to f8adad1 Compare July 13, 2017 10:28
@lutovich lutovich merged commit 2e5b292 into neo4j:1.5 Jul 14, 2017
@lutovich lutovich deleted the 1.5-check-lb-in-stress-test branch July 14, 2017 08:40
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

Successfully merging this pull request may close these issues.

1 participant