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] Fix client not complying with the cluster reconnect strategy #555

Open
3 tasks done
hz-devops-test opened this issue Jun 8, 2022 · 0 comments
Open
3 tasks done

Comments

@hz-devops-test
Copy link

The tracking issue for the Java side PR.

See hazelcast/hazelcast#21568 for details.


This change prevents the client from doing the periodic attempt
for connecting cluster members again when the client is
disconnect from the cluster.

Fixes hazelcast/hazelcast#21565 (https://stackoverflow.com/questions/72538589/hazelcast-client-too-many-logs-when-reconnecting-to-cluster)

Checklist:

  • Labels (Team:, Type:, Source:, Module:) and Milestone set
  • Label Add to Release Notes or Not Release Notes content set
  • Request reviewers if possible
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