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
SQS - Failure to restore unacked messages #1835
Comments
The patch I've done that makes it work as expected is:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Versions:
After seeing messages stuck in
NotVisible
state at our production queues, I've set out to verify the warm shutdown mechanism works properly. My test setup:What I see happens:
received
)NotVisible
stateWarm shutdown
NotVisible
stateExpected behavior: the message should move to
Visible
state.A possible explanation I've found:
By manually changing the code in
kombu/transport/SQS.py
at the_put
function in the casemessage.get('redelivered')
, adding a duplicate call tochange_message_visibility
- the problem seemed to go away. I've tested this against real live SQS and against Localstack. In both the problem was consistent and solved once I added the duplicate call.To sum up, the problem might be on boto3's side and not in kombu, but I'm unsure about this.
I will be happy to assist and make a PR / provide a simple testing scenario.
Thanks
The text was updated successfully, but these errors were encountered: