简体   繁体   English

AWS SQS重新驱动策略,请在队列的末尾进行混乱

[英]AWS SQS redrive policy, which end of the queue do messges go to

In an AWS SQS standard queue you can set a redrive policy which will cause messages to be retried if there is a failure where by the message is not deleted from the queue. 在AWS SQS标准队列中,您可以设置一个重新驱动策略,如果发生故障(该故障不会从队列中删除消息),它将导致重试消息。

In my case i have > 1,000,000 messages on the queue which take a couple of hours to process. 就我而言,我的队列中有> 1,000,000条消息,需要花费几个小时来处理。 When a message fails and is put back on the queue will it be put to the end of the queue or the front. 当消息失败并被放回队列时,它将被放到队列的末尾或最前面。 Will the messages get retried in a minute or two or in two or three hours when all the other messages have been processed? 处理完所有其他消息后,这些消息会在一两分钟或两三个小时后重试吗?

There is no guarantee which order messages are returned, so once you return a message it could be retried immediately, when all the others are processed, or anywhere in the middle - there may be some undocumented common patterns for when retries happen, but its not something you can count on or design around. 无法保证会返回哪些订单消息,因此一旦返回消息,则可以立即重试该消息,在处理所有其他消息时或在中间的任何地方都可以重试-重试发生时可能会有一些未记录的通用模式,但不会您可以依靠或设计的东西。

Q: Does Amazon SQS provide message ordering? 问:Amazon SQS是否提供消息订购?

Yes. 是。 FIFO (first-in-first-out) queues preserve the exact order in which messages are sent and received. FIFO(先进先出)队列保留消息发送和接收的确切顺序。 If you use a FIFO queue, you don't have to place sequencing information in your messages. 如果使用FIFO队列,则不必在消息中放置顺序信息。 For more information, see FIFO Queue Logic in the Amazon SQS Developer Guide. 有关更多信息,请参阅Amazon SQS开发人员指南中的FIFO队列逻辑。

Standard queues provide a loose-FIFO capability that attempts to preserve the order of messages. 标准队列提供了宽松的FIFO功能,该功能尝试保留消息的顺序。 However, because standard queues are designed to be massively scalable using a highly distributed architecture, receiving messages in the exact order they are sent is not guaranteed. 但是,由于标准队列被设计为使用高度分布式的体系结构可大规模扩展,因此无法保证以正确的顺序接收消息。

https://aws.amazon.com/sqs/faqs/ https://aws.amazon.com/sqs/faqs/

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 AWS SQS 死信队列重新驱动策略 - AWS SQS dead-letter queue redrive policy CloudFormation SQS队列Redrive策略依赖于创建的DLQ - CloudFormation SQS Queue Redrive policy dependency on a DLQ created 如果没有设置重新驱动策略,AWS SQS 中的失败消息会发生什么情况? - What happends to a failed message in AWS SQS if there is no redrive policy set? 使用 AWS CLI 命令添加 SQS 重新驱动策略 - Adding SQS redrive policy using AWS CLI command 如何解决为使用 for_each 创建的死信队列添加 SQS 重新驱动策略时的错误消息 - How to resolve the error message when adding SQS redrive policy for deadletter queue created using for_each 为使用 for_each 创建的死信队列添加 SQS 重新驱动策略时如何修复错误消息 - How to fix error message when adding SQS redrive policy for deadletter queue created using for_each SQS批次中的所有消息是否在达到最大redrive(Retry)策略数后都发送到Dead Letter Queue - Are all the messages in SQS batch sent to Dead Letter Queue after reaching the maximum redrive(Retry) policy number SQS Lambda - 重新驱动策略与 DeadLetterConfig - SQS Lambda - Redrive Policy vs DeadLetterConfig AWS SNS 主题子:死信队列(重新驱动策略)权限被拒绝 - AWS SNS Topic Sub: Dead-letter queue (redrive policy) permissions denied 如何使用 Ansible 和 AWS 将重新驱动策略(死信队列/DLQ)添加到 SNS 订阅 - How to add a redrive policy (dead-letter queue / DLQ) to a SNS subscription, with Ansible and AWS
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM