[fix] Bookie Info lost by notification race condition. #20642
According to pulsar's fix: https://github.com/apache/pulsar/pull/20642 race conditions problem is also exists in bk's ZKRegistrationClient.java
Can you provide some information about the process of locating the problem you encountered, or is this just a simple logic synchronization with Pulsar?
@StevenLuMT
After switching the bookie from readonly to writable status online, the broker side continuously generated error logs: "Bookie Handle not available." The issue was resolved only after restarting the bookie. It was discovered that there was a bug in the ZkRegisterClient relied upon by the Pulsar broker, which caused the broker's bookie status cache update to be lost. Although the bookie was actually in a normal state, the broker failed to resolve the bookie's hostname due to the missing cache, resulting in the error: "Bookie Handle not available."
rerun failure checks
rerun failure checks
@gaozhangmin Is it different from this fix #4481
@gaozhangmin Is it different from this fix #4481
it's different case
rerun failure checks