tianshimoyi opened a new issue, #20183: URL: https://github.com/apache/pulsar/issues/20183
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version pulsar v2.9,4 ### Minimal reproduce step When I was doing a data pressure test, due to the large amount of data, the node directly became readOnly before the gc was triggered, and the gc was not executing related configuration: managedLedgerDefaultAckQuorum: "2" managedLedgerDefaultEnsembleSize: "5" managedLedgerDefaultWriteQuorum: "2" managedLedgerMaxEntriesPerLedger: "50000" managedLedgerMaxLedgerRolloverTimeMinutes: "240" managedLedgerMinLedgerRolloverTimeMinutes: "10" gcWaitTime: "300000" majorCompactionInterval: "1500" minorCompactionInterval: "600" ### What did you expect to see? gc worked ### What did you see instead?  ### Anything else? _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]
