Search before asking

• I had searched in the issues and found no similar issues.

What happened

In JdbcRegistry senario.
When a master or worker client shutdown not by gracefully shutdown, the other client within the same registry will not discover this change even if this client is deleted after session timeout.

What you expected to happen

In JdbcRegistry senario.
When a master or worker client shutdown, the other client will discover this change after session timeout.

How to reproduce

1. My configuration registry.type=jdbc
2. Run 2 master clients.
3. Kill master A client with kill -9 PID
4. Wait until the session timeout. Master B will not update the master nodes and the command belong to master A will not be executed by master B.

Anything else

No response

Version

3.3.2

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct