-
Notifications
You must be signed in to change notification settings - Fork 95
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
Active Failover Issue, Driver version 6.6 #342
Labels
Comments
This bug is caused by some design limitations in the Java asynchronous driver. Lines 156 to 182 in 68e9b88
|
It should be fixed by #381 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have an Active Failover cluster which an application is trying to connect to.
The application is using an ArangoDBAsync instance with acquireHostList set to true, and is passed a connection string containing all (3) hosts in the cluster.
However, it seems that the initialisation does not work unless the cluster leader is the first of the 3 hosts in the connection string.
Taking a look at the logs, it looks to me like a connection is opened to the first host, which may be a follower and in this case was, but the log is displaying the leader in the received message.
Only one connection is open, and that's to the follower in this case.
I would expect a new connection to be created to connect with the leader which is returned in the received message but that doesn't seem to be the case.
I'm not sure what I'm missing here. Logs below, in which;
192.168.0.179 - leader.
192.168.0.169, 192.168.0.142 - followers.
The text was updated successfully, but these errors were encountered: