When a BookKeeper is set to readonly, it does not automatically trigger the replication of ledgers to other writable bookkeepers. The readonly state means that the bookie will not accept new writes, but it can still serve read requests. Replication of ledgers typically occurs when a bookie fails or is decommissioned, and the system identifies under-replicated ledgers that need to be replicated to maintain the desired replication factor.
If you want to ensure that ledgers on a readonly bookie are replicated to other writable bookies, you would need to manually trigger the replication process or adjust the configuration to handle such scenarios. This might involve using tools or commands to list under-replicated ledgers and initiate their replication. Would you like more details on how to manage this process?
Sources:
-
Bookkeeper decommission may be blocked by ledgers that cannot be replicated 👍 0 button 👎 0 button 💡
Hint: Mention @runllm in the thread for followups.