🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
What is the expected outcome if failover happens while replay is in progress
Hi,
Consider a scenario where a Queue listener (JCSMP) is listening with CLIENT_ACK, typically a slow consumer processing the messages in the queue at a rate slower than producer in a guaranteed messaging approach with replay enabled.
What happens if failover is triggered while replay is in progress on a slow consumer which will typically have a queue depth and also replay messages being processed at a slower rate both at the same time.
Any thoughts?
Thanks
Best Answer
-
Hello @rdesoju, an interesting question. I haven't tried this myself, but I'll go it a go on Monday. Since PubSub+ replicates all state, including meta-data, on messages and queues, the backup node will know:
- that replay has been initiated on the queue;
- exactly where the consumer has got to in the replayed queue of messages.
So, I am pretty confident the consumer will pick up where it left off.
Remember that replay re-sets the JSCMP flow state between the broker and the consumer, as the consumer will be in a different place in the queue once replay is initiated - for reasons like this. So actually, the consumer being slow doesn't really affect this case.
Now, if your question is: my consumer didn't catch up with the queue, then replay is initiated, what happens to the new messages that didn't get to the consumer before replay is initiated? Well, they will just appear in the queue of messages in order and will be delivered from the queue as replay completes - just like any other new message, say one queued while replay is still replaying old messages. Failover doesn't change any of this, because of the reasons above.
5
Answers
-
Hello @rdesoju, an interesting question. I haven't tried this myself, but I'll go it a go on Monday. Since PubSub+ replicates all state, including meta-data, on messages and queues, the backup node will know:
- that replay has been initiated on the queue;
- exactly where the consumer has got to in the replayed queue of messages.
So, I am pretty confident the consumer will pick up where it left off.
Remember that replay re-sets the JSCMP flow state between the broker and the consumer, as the consumer will be in a different place in the queue once replay is initiated - for reasons like this. So actually, the consumer being slow doesn't really affect this case.
Now, if your question is: my consumer didn't catch up with the queue, then replay is initiated, what happens to the new messages that didn't get to the consumer before replay is initiated? Well, they will just appear in the queue of messages in order and will be delivered from the queue as replay completes - just like any other new message, say one queued while replay is still replaying old messages. Failover doesn't change any of this, because of the reasons above.
5
