<@U078Y59KC3B> is the configuration field `managed...
# ask-ai
t
@RunLLM is the configuration field
managedLedgerForceRecovery
valid in the broker configuration in the
4.x
version?
r
Yes, the configuration field
managedLedgerForceRecovery
is valid in the broker configuration for Pulsar 4.x. It is used to allow brokers to forcefully recover managed ledgers by skipping ledger failures, which is helpful in disaster recovery scenarios. This field is present and documented in the relevant configuration files and code for recent versions, including 4.x, and is referenced in recent issues and tests as a dynamic configuration option for managed ledgers. See ServiceConfiguration.java and ManagedLedgerConfig.java. Would you like more detail on how to use or set this configuration? Sources: - ServiceConfiguration.java - ManagedLedgerConfig.java 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.
t
@RunLLM How is
managedLedgerForceRecovery
set in the broker configuration?
r
It seems likely that
managedLedgerForceRecovery
is set in the broker configuration file (typically
broker.conf
) as a boolean property, for example:
managedLedgerForceRecovery=true
. This enables the broker to forcefully recover managed ledgers by skipping ledger failures. The property can also be updated dynamically via Pulsar's dynamic configuration system. See ServiceConfiguration.java. Would you like more detail on dynamic updates or operational impact? Sources: - ServiceConfiguration.java 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.
t
@RunLLM yes
r
You can update
managedLedgerForceRecovery
dynamically on a running broker using the Pulsar admin CLI or compatible tools. The command is:
Copy code
pulsar-admin brokers update-dynamic-config --config managedLedgerForceRecovery --value true
This change takes effect without restarting the broker. The same can be done with tools like
pulsarctl
using similar flags. For more, see Pulsar admin API docs and pulsarctl docs. Sources: - pulsarctl docs 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.