New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix snsqs redelivery #104
Fix snsqs redelivery #104
Conversation
@Nyholm can this be merged? |
Sorry for all the questions. Do I understand it correctly that if you are using I imagined Snsqs to be like AMQP fanout. Ie, you have multiple queues. They way I see it (Im probably wrong) the What Im asking is: How are we sure that we republish the message on the correct queue? |
@Nyholm you're right, it's similar to AMQP fanout — we configure a SNS topic to send messages to and a SQS queue (subscribed to the topic) to receive them. Now maybe I misunderstood something but I thought you could configure only one queue using this messenger enqueue transport lib (coming from DSN indeed, like If we can configure multiple queues here, how do we do it? |
@Nyholm sorry for pushing this :) what can I do to help this get further? |
But with this configuration causes an issue if we merge this PR, right? You write to SNS topic Foobar. That will fan out to SQS queue A, B and C. If consumer for queue B fail, you want to repost the message to queue B. Not to Foobar. With a DSN like in your example, you will always put the message back to the same queue, no matter from where it came from. It is too static, right? |
If I understand correctly:
If this is right, the retry message goes back to the queue where it came from. Does it make sense? |
HM. If you now use DSN So if your app should read from SQS A and B you need two different DSN, right? My worry was that it does not choose queue automatically. But I (think I) understand now that you always has to hard code the queue to read from. |
Exactly, I couldn't make it work properly without providing both topic and queue in the DSN. |
@Nyholm what can I do to help this get further? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. Sorry for my slow responses and slow mind.
This all look good. Thank you
Great news, thank you! Can we also get a release? |
When resending a message for retry on enqueue/snsqs transport, we need to send the message to the queue rather than the topic.