Paragrf opened a new issue, #3385: URL: https://github.com/apache/kvrocks/issues/3385
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/kvrocks/issues) and found no similar issues. ### Motivation I've observed that when the Controller detects a down slave node, it does not push this status update to the rest of the cluster. Consequently, clients are unable to receive topology updates through the server and must rely on their own health checking and traffic shedding mechanisms. This is problematic for simpler clients that lack sophisticated detection logic. ### Solution Would it be more effective for KVRocks to maintain consistency with Redis behavior in this scenario? I suggest we introduce a new command or modify existing interfaces to allow the Controller to push "node down" information to the surviving KVRocks nodes. By doing so, clients can retrieve the updated cluster state directly from the remaining active nodes, thereby accelerating topology updates and minimizing the impact of node failures. ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
