Support for x-consumer-timeout in RabbitMQ

[pyjads]

Summary

Introduce a new queue argument x-consumer-timeout in RabbitMQ to allow users to specify a maximum time a message can be processed by a consumer before it is considered unacknowledged. This feature aims to provide greater control over message processing times and improve the handling of slow consumers.

Description

In current RabbitMQ implementations, managing the time a consumer spends processing a message relies on a combination of client-side logic and RabbitMQ's heartbeat mechanism. However, these methods do not directly address scenarios where a consumer might be taking too long to process a single message, potentially leading to message processing delays and inefficiencies in resource utilization.

The proposed x-consumer-timeout feature would allow users to set a timeout value (in milliseconds) at the queue level. This timeout would define the maximum allowed time for a consumer to process a message after it has been delivered and before it acknowledges the message back to RabbitMQ. If the consumer fails to acknowledge the message within this timeframe, RabbitMQ would automatically requeue the message, making it available for redelivery to the same or a different consumer.

More Details on Consumer Timeout

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

[pyjads]

Any updates on the request?