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

[TRACKING ISSUE] Introduce a property to control the reconnection behavior of the client [API-2036] #635

Open
hz-devops-test opened this issue Jun 9, 2023 · 0 comments

Comments

@hz-devops-test
Copy link

The tracking issue for the Java side PR.

See hazelcast/hazelcast#24772 for details.


During reconnections, the client would normally try to connect to the last known member list, and then try the configured member addresses.

This logic is fine for most of the use cases, but for some users who expose their multi-member clusters via a single load balancer or node port, this might not be what we want. In their use cases, cluster members are not accessible from the client directly, the connection has to be established by the service in front of the cluster members.

For such scenarios, not trying to connect to the members from the last known member list is probably what we want.

We decided not to change the default behavior, or be smart and try to detect such cases. Instead, we decided to introduce a private property for now, and share that with the customer that wants this feature. In the future, depending on the feedback and our own discussions, we might promote this to a public property as well.

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

1 participant