The LoadbalanceRSocketClient cannot participate in load balancing calculations after the service node is restored

[LiuYawei2019]

Based on the rsocket-java 1.1.3 version, the implementation of the LoadbalanceRSocketClient was tested. It was observed that after a service node went down, the client's load balancer successfully removed the node, ensuring that subsequent requests were not directed to the failed node. However, when the failed node resumed service, it was not promptly reintegrated into the load balancing mechanism.

Expected Behavior

It is expected that once the failed node recovers, the client can detect and reintegrate the node into the load balancing pool, thereby restoring the node's ability to handle requests.

Actual Behavior

Steps to Reproduce

For running the demo, please refer to https://github.com/LiuYawei2019/rsocketDemo.

Possible Solution

Your Environment

• RSocket version(s) used: 1.1.3
• Other relevant libraries versions (eg. netty, ...):
• Platform (eg. JVM version (javar -version) or Node version (node --version)): JDK17
• OS and version (eg uname -a): Darwin MacBookPro 21.6.0 Darwin Kernel Version 21.6.0: Mon Dec 19 20:44:01 PST 2022; root:xnu-8020.240.18~2/RELEASE_X86_64 x86_64