@RunLLM Failed to perform http post request: org.apache.pulsar.shade.javax.ws.rs.ClientErrorException: HTTP 412 Failed for Subscription Busy: Failed to fence subscription

The error "HTTP 412 Failed for Subscription Busy: Failed to fence subscription" means the subscription is currently busy—likely due to active consumers or ongoing operations—so Pulsar cannot perform the requested action (such as reset cursor or delete) because it cannot "fence" (lock) the subscription for exclusive access. This is a known behavior in Pulsar when a subscription is in use or not fully disconnected, and the operation is retried or fails with this error until the subscription is free. According to PersistentTopics.java, this is returned as a precondition failure (HTTP 412) when the subscription cannot be fenced. Would you like more detail on how to resolve or avoid this error? Sources: - PersistentTopics.java 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@RunLLM need how to resolve this error

To resolve "HTTP 412 Failed for Subscription Busy: Failed to fence subscription," ensure all consumers on the subscription are disconnected before retrying the operation. This error occurs when active consumers prevent the broker from fencing the subscription for exclusive actions like reset or delete. Wait for consumers to disconnect, or manually close them, then retry the command. If you need to forcefully delete a subscription, use the

force

option (if available), but note that on persistent topics, this may still fail if consumers are connected, as described in PersistentTopics.java and Pulsar issue #22404. Would you like more detail or example commands? Sources: - PersistentTopics.java - Pulsar issue #22404 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.