- Newest
- Most votes
- Most comments
Hi
please check these steps to resolve issue:
Check the Queue Length and Visibility Timeout:
*** Queue Length:** Use the AWS Management Console or CLI to monitor the queue length. A consistently high number of messages might indicate that your consumers (workers processing jobs) can't keep up.
-
Visibility Timeout: This setting controls how long a message is invisible to other consumers after being received by one. A low timeout could lead to messages being redelivered before the first consumer finishes processing them. Review the visibility timeout and adjust if necessary. The maximum is 12 hours.
-
Consumer Health: Ensure your consumers are healthy and running. Check for any errors or exceptions that might be preventing them from processing messages. Utilize monitoring tools or logs to identify issues.
-
Stuck Messages: Use the ApproximateReceiveCount attribute of the queue to identify messages that have been received but not deleted for a long time. This could indicate processing issues with specific messages.
-
Logging: Implement robust logging within your consumers to capture processing details and identify any errors or exceptions.
-
**Monitoring: **Set up monitoring for your SQS queue and consumers to track key metrics and receive alerts for potential issues.
Usually when you do not get all the messages in the consumer is because you have an additional consumer reading from the same queue. Make sure that you do not have another process reading from the same queue, or that you did not configured a Lambda function to trigger from the queue.
Another option might be that you are reading messages in batches, but you only process the first message in the batch.
What do you mean by processing jobs? Have you set your SQS queue to trigger a Lambda function, for example, based on messages arriving in the queue, or is your application polling for messages from SQS, or what is it that is expected to happen but apparently not always happening?
Hi Leo K,
Thank you for replying.I am not using Lambda function, the issue is message is arrives to Queue, most of the messages not processing, only few messages are processing.
Hi rePost-User-3706207, please specify what type of processing you are expecting to happen that isn't happening. What technical mechanism is used to receive the messages from the queue?
Relevant content
- asked 5 months ago
- asked 2 years ago
- asked 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Dear @Garee Sandeep,
Thank you for replying , i will definitely look in to these options.