StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Over a year later, it seems that our issue has been resolved. The key takeaways seem to be:</p> <ul> <li>Make sure you have a solid DNS system so when MSMQ needs to resolve a host, it can.</li> <li>Only create one clustered instance of MSMQ on a Windows Failover Cluster.</li> </ul> <p>When we set up our Windows Failover Cluster, we made the assumption that it would be bad to "waste" resources on the inactive node, and so, having two quasi-related NServiceBus clusters at the time, we made a clustered MSMQ instance for Project1, and another clustered MSMQ instance for Project2. Most of the time, we figured, we would run them on separate nodes, and during maintenance windows they would co-locate on the same node. After all, this was the setup we have for our primary and dev instances of SQL Server 2008, and that has been working quite well.</p> <p>At some point I began to grow dubious about this approach, especially since failing over each MSMQ instance once or twice seemed to always get messages moving again.</p> <p>I asked <a href="http://www.udidahan.com/" rel="nofollow">Udi Dahan</a> (author of NServiceBus) about this clustered hosting strategy, and he gave me a puzzled expression and asked "Why would you want to do something like that?" In reality, the Distributor is very light-weight, so there's really not much reason to distribute them evenly among the available nodes.</p> <p>After that, we decided to take everything we had learned and <a href="http://www.make-awesome.com/2010/10/deploying-nservicebus-in-a-windows-failover-cluster/" rel="nofollow">recreate a new Failover Cluster with only one MSMQ instance</a>. We have not seen the issue since. Of course, making sure this problem is solved would be proving a negative, and thus impossible. It hasn't been an issue for at least 6 months, but who knows, I suppose it could fail tomorrow! Let's hope not.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload