amjadali-klarity opened a new issue, #25433: URL: https://github.com/apache/pulsar/issues/25433
### Search before reporting - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [x] I understand that [unsupported versions](https://pulsar.apache.org/contribute/release-policy/#supported-versions) don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### User environment Pulsar Version: 4.1.2 (Image: docker.io/apachepulsar/pulsar-all:4.1.2) Platform: Kubernetes (Azure/AKS based on log headers) Component: BookKeeper / ZooKeeper ### Issue Description Our pulsar-bookie pods are experiencing sudden restarts. The logs indicate that the ZKRegistrationClient is invalidating the cache for the specific bookie address, followed by NetworkTopologyImpl removing the node from the /default-rack. ### Error messages ```text INFO org.apache.bookkeeper.discover.ZKRegistrationClient - Invalidate cache for pulsar-bookie-1.pulsar-bookie.pulsar.svc.cluster.local:3181 INFO org.apache.bookkeeper.net.NetworkTopologyImpl - Removing a node: /default-rack/pulsar-bookie-1.pulsar-bookie.pulsar.svc.cluster.local:3181 ``` ### Reproducing the issue ZooKeeper logs show standard ruok commands but no explicit session expiration immediately preceding the drop. The Bookie seems to be under normal load (Compaction usage buckets are mostly at 100%). Config: diskUsageWarnThreshold = 0.9, isForceGCAllowWhenNoSpace = true. ### Additional information _No response_ ### Are you willing to submit a PR? - [ ] 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]
