bug: version 5.2.0 breaks celery with sqs msg processing

Open onikonychev opened this issue 2 years ago • 3 comments

After yesterday's upgrade to 5.2.0 I noticed that messages enqueue (through Celery) to SQS moves messages directly to "In flight", worker doesn't even see them. I found my queue full of 120000 messages in flight and completely stuck.

Downgraded to 5.1.1 and workers started processing messages normally.

Nov 10 '23 10:11 onikonychev

is SQS a amqp broker?

Nov 10 '23 12:11 auvipy

is SQS a amqp broker?

yes, it's AWS. See: https://docs.celeryq.dev/en/latest/getting-started/backends-and-brokers/sqs.html

Nov 10 '23 12:11 onikonychev

you should pin botocore to 1.31.80 or below to get rid of this bug

Nov 14 '23 12:11 auvipy