search

hazelcast / hazelcast-nodejs-client

Hazelcast Node.js Client
https://hazelcast.com/clients/node-js/
Apache License 2.0
150 stars 58 forks source link

[TRACKING ISSUE] Continue trying if initial membership event retrieval fails and client is failover [API-2171] #1515

Open hz-devops-test opened 9 months ago

hz-devops-test commented 9 months ago

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