You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 18, 2025. It is now read-only.
// PersistentAllSubscriptionOptions options for most of the persistent subscription requests.
type PersistentAllSubscriptionOptions struct {
...
// Requires the request to be performed by the leader of the cluster.
RequiresLeader bool
}
I am just curious, why is there an option for RequiresLeader when the docs state the following:
Persistent subscriptions only run on the Leader node. This means that more pressure will be put on the Leader node, and there is no option to balance the load to a follower like with a Catch-up subscription.
Is there a use case for this option or should I default to setting it to true?
I am just curious, why is there an option for
RequiresLeaderwhen the docs state the following:Is there a use case for this option or should I default to setting it to true?