ckdarby opened a new issue #16: URL: https://github.com/apache/pulsar-helm-chart/issues/16
**Describe & Reproduce** Steps to reproduce the behavior: 1. Create another node group 2. Attempted graceful node transfer 3. Issue happened where multiple nodes terminated and basically major amounts of Pulsar was impacted probably breaking the pod disruption budget 4. Get Pulsar back up, all storage mounts, cluster decides those are abandoned at some point while other bookies come back online and I guess marks them for garbage collection? **Expected behavior** When cluster goes into an unstable state it doesn't take it upon itself to begin deleting Ledgers? Here are the logs of the bookie that looked like it was up during the unstableness [delete.txt](https://github.com/apache/pulsar-helm-chart/files/4693087/delete.txt) ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
