Skip to content

fix: add missing managedLedgerForceRecovery broker configuration field #24672

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
thomas-bousquet wants to merge 2 commits into
base: master
Choose a base branch
from
Open

fix: add missing managedLedgerForceRecovery broker configuration field #24672

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fa0c373
fix: add missing managedLedgerForceRecovery broker configuration field
thomas-bousquet Aug 26, 2025
2bc5061
fix: add missing managedLedgerForceRecovery standalone configuration …
thomas-bousquet Aug 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions conf/broker.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1360,6 +1360,10 @@ managedLedgerInfoCompressionThresholdInBytes=16384
# corrupted at bookkeeper and managed-cursor is stuck at that ledger.
autoSkipNonRecoverableData=false

# Whether to allow brokers to forcefully load topics by skipping ledger failures to avoid topic unavailability and
# perform auto repairs of the topics.
managedLedgerForceRecovery=false

# Whether to recover cursors lazily when trying to recover a managed ledger backing a persistent topic.
# It can improve write availability of topics.
# The caveat is now when recovered ledger is ready to write we're not sure if all old consumers last mark
Expand Down
Loading