MSMQ群集在故障转移时丢失消息 [英] MSMQ Cluster losing messages on failover

查看:119
本文介绍了MSMQ群集在故障转移时丢失消息的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个MSMQ群集设置,其中包含共享驱动器的节点(主动/被动).

I've got a MSMQ Cluster setup with nodes (active/passive) that share a drive.

这是我正在执行的测试.我将消息发送到可恢复的队列.然后,我使MSMQ群集组脱机,然后再次使其联机.

Here are the tests I'm performing. I send messages to the queue that are recoverable. I then take the MSMQ cluster group offline and then bring it online again.

结果:消息仍然存在.

然后我通过将组移至节点2来模拟故障转移.移入成功,但是消息不存在.

I then simulate failover by moving the group to node 2. Moves over successfully, but the messages aren't there.

我将消息发送为可恢复,并且MSMQ群集组具有一个两个节点都可以访问的驱动器.

I'm sending the messages as recoverable and the MSMQ cluster group has a drive that both nodes can access.

有人吗?

更多信息:

Quorum驱动器仅停留在节点1上.

The Quorum drive stays only on node 1.

我有两个服务/应用组.一个MSMQ,另一个是通用服务组.

I have two service/app groups. One MSMQ and one that is a generic service group.

更多信息:

当节点1处于活动状态时,我将其充满消息.故障转移到节点2.队列中出现0消息,消息为02.然后我故障转移回01,消息在01中.

When node 1 is active, I pump it full of messages. Failover to node 2. 0 message in the queue for 02. Then I failover back to 01, and the messages are in 01.

推荐答案

您尚未对MSMQ进行群集或未正确使用群集的MSMQ. 您正在查看的是本地MSMQ服务.

You haven't clustered MSMQ or aren't using clustered MSMQ properly. What you are looking at are the local MSMQ services.

http: //blogs.msdn.com/b/johnbreakwell/archive/2008/02/18/clustering-msmq-applications-rule-1.aspx

欢呼 约翰

=================================

==================================

好吧,也许所使用的驱动器号未统一实施.

OK, maybe the drive letter being used isn't consistently implemented.

  1. 群集MSMQ正在使用的存储位置是什么?
  2. 如果同时从节点1和节点2在资源管理器中打开此存储位置,文件夹内容是否完全相同?如果您通过节点1的资源管理器"窗口创建文本文件,刷新后是否会在节点2的资源管理器"窗口中显示该文本文件?

这篇关于MSMQ群集在故障转移时丢失消息的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆