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.

Sign up for GitHub

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

Jump to bottom

Initiate reconnect for DiscoveryClusterAddressProvider #163

Closed
wey1and opened this issue Jan 31, 2022 · 0 comments · Fixed by #167
Closed

Initiate reconnect for DiscoveryClusterAddressProvider #163

wey1and opened this issue Jan 31, 2022 · 0 comments · Fixed by #167
Assignees
@wey1and
Labels
bug Something isn't working customer

Comments

@wey1and
Copy link
Contributor

wey1and commented Jan 31, 2022

When receiving a status that indicates to us that the node is unavailable from ServerNodeInfo in DiscoveryClusterAddressProvider, the driver does not initiate a reconnect, thereby not taking the current list of addresses. It is necessary to initiate reconnection to the nodes in case of failure of at least one node.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wey1and wey1and

Labels
bug Something isn't working customer
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added refresh callback to address provider tarantool/cartridge-java
1 participant
@wey1and