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.

Sign up for GitHub

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

Jump to bottom

risk of getting empty messages #12

Open

jingpengw opened this issue Jan 22, 2019 · 1 comment

Assignees

Member

jingpengw commented Jan 22, 2019 •

edited

sqs can return empty messages if the message number is low (<1000), maybe this explains that why the last few hundred tasks takes longer time.

this package set the wait time to be 0, and could potentially get empty messages.
https://github.com/seung-lab/python-task-queue/blob/master/taskqueue/aws_queue_api.py#L60

here is the documentation of the long polling:
https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-long-polling.html
https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/working-with-messages.html#setting-up-long-polling

as suggested, simply setting the waittime to 20 seconds should fix this.

jingpengw assigned william-silversmith

Contributor

william-silversmith commented Jul 24, 2020

Wait time has been set to 20 sec since a355d04

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment