| Author |
Message
|
| Andy |
 Posted: Wed Jan 05, 2005 6:31 am Post subject: Urgent: Failover and Load balancing |
 |
|
Centurion
Joined: 14 May 2003
Posts: 122
|
I am learning WebSphere MQ and want to do clustering. We are looking for follwoing setup:2
Machine A- cluster QM1,RQM1(full repository QM)
Machine B-cluster QM2,RQM2(full repository QM )
Does this architecture supports Loadbalancing and Failover
By Loadbalancing I mean that if 10 requests comes, 5 requests will be serverd by QM1 and rest 5 by QM2
By failover I mean that if QM1 is down, QM2 will handle the request.
I have searched and seen post related to failover and loadbalancing and already going through documents but still need more time to understand it fully.
Also, it would be helpful if somebody can suggest the impacts of having Microsoft NLB in place for these 2 machines?
Thanks in advance
_________________
 Andy |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jan 05, 2005 6:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can't use an NLB with WebSphere MQ Channels. MQ Channels keep synchronized with the other end. If you try to use an NLB to change one end, the channels fall over.
Your architecture supports Load Balancing.
It does not support Failover. YES, the other queue manager will handle *new* requests. But that's it. Client applications connected to the old machine will need to manually reconnect to the other machine. (this is true with hardware clustering too, the client connection will need to be reestablished - but it will be made with the same information not new information)
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kingsley |
| Posted: Wed Jan 05, 2005 8:14 am Post subject: this is true with hardware clustering too, the client connec |
|
|
Disciple
Joined: 30 Sep 2001
Posts: 175
Location: Hursley
|
this is true with hardware clustering too, the client connection will need to be reestablished - but it will be made with the same information not new information.
---------------
This is not true as in hardware cluster you will be creating a Virtual Queuemanager with a virtual IP. Hence client apps need not re connect.
Incase of MQSeries cluster, if the client is connected to a QueueManager that is part of cluster, then they need not reconnect unless the connected queuemanager is down. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 05, 2005 8:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Umm.
There will be some period of time while the machine is failing over. During that period of time, I do not believe that the client connection will be active. I believe it will get disconnected, and have to be reconnected.
Maybe I am wrong.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 05, 2005 10:01 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
Jeff, you are correct. The apps will have to reconnect, although they can just use the same connection info.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Andy |
| Posted: Thu Jan 06, 2005 9:52 pm Post subject: |
|
|
Centurion
Joined: 14 May 2003
Posts: 122
|
Thanks everybody. It was very helpful.
_________________
Andy |
|
| Back to top |
|
|
|
|
