hazelcast / hazelcast/hazelcast-csharp-client
[TRACKING ISSUE] Continue trying if initial membership event retrieval fails and client is failover [API-2171]
Open
- Dominant language
- C#
- Stars
- 107
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
The tracking issue for the Java side PR.
See https://github.com/hazelcast/hazelcast/pull/26009 for details.
---
As reported in https://hazelcast.atlassian.net/browse/API-2171, the client was not continuing trying next clusters if the connected cluster fails to send initial membership event in time. I added a check about client being failover in the conn. manager and conditionally handle the case.
This PR also adds required internal getters/APIs used in the test FailoverClusterMembershipEventTest in the EE PR https://github.com/hazelcast/hazelcast-enterprise/pull/6874
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.