@RunLLM When is a subscription reset? I'm trying to understand the description in a Git issue that says

When resetting a subscription

A subscription reset in Pulsar refers to moving the subscription's cursor to a specific position, either by message ID or timestamp. This operation is typically performed to reprocess messages or recover from issues, and can be triggered using admin tools or APIs such as

reset-cursor

or

seek

commands, which reposition the subscription to the desired point in the topic's message log. For example, you can reset a subscription to the earliest, latest, or a specific message, or to the closest message after a given timestamp, using commands like

pulsar-admin topics reset-cursor

or

pulsarctl seek

(Pulsar Admin Reference, pulsarctl seek). Would you like more detail on how to perform a subscription reset or on the internal mechanics of what happens during a reset? Sources: - Pulsar Admin Reference - pulsarctl seek 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.