简体   繁体   English

Azure Service Bus主题订阅服务器接收消息的顺序不正确

[英]Azure Service Bus Topic Subscriber receiving messages not in order

I am using azure service bus topic and I have enable session for it's subscription. 我正在使用azure服务总线主题,并且已为其订阅启用会话。

With in the my logic app i am inserting data using sql transaction which are coming from topic I am using topic Subscription(peek-lock) and in subscriber level concurrency is set to default as follows 在我的逻辑应用程序中,我使用来自主题的sql事务插入数据,我使用主题Subscription(peek-lock),在订户级别中,并发性设置为默认值,如下所示

在此处输入图片说明

According to my Understanding, my logic app(subscriber) should read ALL the messages and have to processed in FIFO 根据我的理解,我的逻辑应用程序(订户)应读取所有消息,并必须在FIFO中进行处理
my logic app is like 我的逻辑应用程序就像

在此处输入图片说明

which means it should insert data to the table in ordered manner 这意味着它应该按有序方式将数据插入表中

however when i checked in the trigger log it shows correct order but in database level you can see the order is not happening 但是,当我检查触发器日志时,它显示了正确的顺序,但是在数据库级别,您可以看到该顺序未发生

在此处输入图片说明

Message ordering is a delicate business. 消息订购是一项微妙的业务。 You can have either message ordering or concurrent processing, but not both. 您可以进行消息排序或并发处理,但不能同时进行。 The moment you make message ordering a must, you lose the ability to have concurrent processing. 一旦必须订购消息,就失去了进行并发处理的能力。 This is correct for both, Azure Service Bus Sessions and Logic Apps concurrency control. 这对于Azure Service Bus会话和Logic Apps并发控制都是正确的。 You could process multiple sessions , but each session would be still restricted to a single processor. 您可以处理多个会话 ,但是每个会话仍将限于一个处理器。 Here's a post about it. 这是有关它的帖子

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

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