ThomasTaketurns opened a new issue, #21987: URL: https://github.com/apache/pulsar/issues/21987
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version 3.0.0 ### Minimal reproduce step - Stop some bookie - Some ledgers become under replicated as we can see in pulsar-recovery-0 logs - Ledgers are not rereplicated ### What did you expect to see? I would expect the ReplicationWorker thread on pulsar-recovery-0 pod to trigger rereplication of under replicated nodes. ### What did you see instead? I do not see any log from the ReplicationWorker thread. I can see the Auditor thread being able to list under replicated ledgers though. ### Anything else? Please find attached the logs from taketurns-pulsar-recovery-0 when I stop som bookie. [recoveryLogs.txt](https://github.com/apache/pulsar/files/14085300/recoveryLogs.txt) Please also notice that the recovery process is triggered when I redeploy taketurns-pulsar-recovery-0 on my K8S cluster. 2024-01-29T13:34:29,525+0000 [ReplicationWorker] INFO org.apache.bookkeeper.replication.ReplicationWorker - Ledger replicated successfully. ledger id is: 548080 I may be missing some configuration here. I would like to understand for what reason does the ReplicationWorker thread does not start to rereplicate ledgers when some have been identified as underreplicated by the auditor and how could I make it automatic without needing to restart the recovery pod. Thanks for your precious help, Thomas @ Taketurns ### 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]
