简体   繁体   English

Azure自动缩放队列包括死信

[英]Azure Auto-scaling Queue includes Dead Letter

I have a worker role with auto-scaling turned on according to queue length on a Service Bus queue. 我有一个工作人员角色,根据服务总线队列上的队列长度启用了自动缩放功能。 I noticed that my role instances seem to stay scaled up even where there are 0 active items in the queue but several in the dead letter queue. 我注意到,即使队列中有0个活动项目,而死信队列中有几个活动项目,我的角色实例似乎也保持扩展状态。

The metric "Length" on the old portal graph includes the dead letter items. 旧门户网站图上的度量标准“长度”包括死信项目。 However, it doesn't make sense that the system would scale based on dead letters. 但是,根据死信扩展系统是没有意义的。

Does anyone know if there is an official statement or documentation on this? 有人知道这方面是否有官方声明或文件?

You could leverage auto-forwarding to centralize all of your DLQed messages. 您可以利用自动转发来集中所有DLQed消息。 This will ensure that your source queues/subscription only contain the messages to be processed. 这将确保您的源队列/订阅仅包含要处理的消息。 That way your cloud service can scale accurately, based on the number of messages to be processed, without counting DLQed messages in. 这样,您的云服务就可以根据要处理的消息数准确扩展,而无需计算DLQed消息。

Note: your messages will be moved to a centralized DLQ, but will still contain information about source queue. 注意:您的消息将被移至集中式DLQ,但仍将包含有关源队列的信息。 You'll find more info here . 您可以在此处找到更多信息。

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

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM