You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When we process a batch of SQS messages, we wait for some time before processing next batch. The wait time is based on number of messages processed and poll time. If poll time is greater than 0 and maximum messages is default value (which is 10 and it's the maximum value) SQS worker will quite likely have a delay because SQS might never return maximum number of messages.
SQS will return as soon as it gets at least one message even if maximum messages is set to 10.
if (messagesProcessed < sqsOptions.getMaximumMessages() && s3SourceConfig.getSqsOptions().getPollDelay().toMillis() > 0) {
Expected behavior
SQS should wait if at least one message is processed instead of checking against maximum messages.
The text was updated successfully, but these errors were encountered:
asifsmohammed
changed the title
[BUG] S3 Source poll delay will always call Thread.sleep() if greater than 0
[BUG] S3 Source poll delay will always call Thread.sleep() if poll delay is greater than 0
Jun 29, 2022
Describe the bug
When we process a batch of SQS messages, we wait for some time before processing next batch. The wait time is based on number of messages processed and poll time. If poll time is greater than 0 and maximum messages is default value (which is 10 and it's the maximum value) SQS worker will quite likely have a delay because SQS might never return maximum number of messages.
SQS will return as soon as it gets at least one message even if maximum messages is set to 10.
if (messagesProcessed < sqsOptions.getMaximumMessages() && s3SourceConfig.getSqsOptions().getPollDelay().toMillis() > 0) {
Expected behavior
SQS should wait if at least one message is processed instead of checking against maximum messages.
The text was updated successfully, but these errors were encountered: