| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| clustering across multiple data centers |
« View previous topic :: View next topic » |
| Author |
Message
|
| gbaddeley |
 Posted: Thu Feb 22, 2018 6:07 pm Post subject: Re: clustering across multiple data centers |
 |
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| mq__quest wrote: |
| Is building a MQ cluster across 2 data centers a good idea? could there be network and latency issues? |
I am OK with this design, we use it, though data centers are only 20 miles apart and we have redundant 10 GBPS dedicated links between them.
If you have any concern about network reliability, ask the nw team about redundancy, network capacity and SLAs.
You should have a pre-prod / QA / SVT environment that will have same setup as intended in Prod, and you do satisfactory load / performance / failover testing.
MQ Client apps should preferrably connect to the most local qmgr (in the same data center) for best performance and reliability.
_________________
Glenn |
|
| Back to top |
|
 |
| mq__quest |
| Posted: Wed Apr 25, 2018 5:23 pm Post subject: |
|
|
Apprentice
Joined: 21 Aug 2017
Posts: 49
|
| bruce2359 wrote: |
| Replicated (mirrored) hot-site - one transaction, one cluster, is another possibility. I sense that the OP is uncertain here. |
sorry for the delayed response. Yes, DCs are hot-sites. Could you explain what you mean by one transaction please? |
|
| Back to top |
|
|
| mq__quest |
| Posted: Wed Apr 25, 2018 5:32 pm Post subject: Re: clustering across multiple data centers |
|
|
Apprentice
Joined: 21 Aug 2017
Posts: 49
|
| gbaddeley wrote: |
| mq__quest wrote: |
| Is building a MQ cluster across 2 data centers a good idea? could there be network and latency issues? |
I am OK with this design, we use it, though data centers are only 20 miles apart and we have redundant 10 GBPS dedicated links between them.
If you have any concern about network reliability, ask the nw team about redundancy, network capacity and SLAs.
You should have a pre-prod / QA / SVT environment that will have same setup as intended in Prod, and you do satisfactory load / performance / failover testing.
MQ Client apps should preferrably connect to the most local qmgr (in the same data center) for best performance and reliability. |
Whats the best way to achieve HA and DR with this (2 DCs 1 Cluster ) Setup? |
|
| Back to top |
|
|
| mq__quest |
| Posted: Fri May 11, 2018 9:09 am Post subject: |
|
|
Apprentice
Joined: 21 Aug 2017
Posts: 49
|
| does multi-instance qmgrs serve the purpose of both HA and DA in this case? |
|
| Back to top |
|
|
| exerk |
| Posted: Fri May 11, 2018 1:19 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mq__quest wrote: |
| does multi-instance qmgrs serve the purpose of both HA and DA in this case? |
No, MI is a High-Availability solution, but you might want to look into Disaster Recovery Replicated Data Queue Managers (DRRDQMs) as introduced in V9.0.5 CD.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| MQMB&WAS |
| Posted: Wed May 23, 2018 9:35 am Post subject: Re: clustering across multiple data centers |
|
|
Centurion
Joined: 12 Jun 2016
Posts: 130
|
| gbaddeley wrote: |
I am OK with this design, we use it, though data centers are only 20 miles apart and we have redundant 10 GBPS dedicated links between them.
If you have any concern about network reliability, ask the nw team about redundancy, network capacity and SLAs.
You should have a pre-prod / QA / SVT environment that will have same setup as intended in Prod, and you do satisfactory load / performance / failover testing.
MQ Client apps should preferrably connect to the most local qmgr (in the same data center) for best performance and reliability. |
Glenn, if the apps don't connect to all of its available qmgrs(to put), would't it cause throughput issues ? and what happens to the msgs when a app connecting to only 1 qmgr(to get) goes down? |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed May 23, 2018 3:52 pm Post subject: Re: clustering across multiple data centers |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| MQMB&WAS wrote: |
| gbaddeley wrote: |
I am OK with this design, we use it, though data centers are only 20 miles apart and we have redundant 10 GBPS dedicated links between them.
If you have any concern about network reliability, ask the nw team about redundancy, network capacity and SLAs.
You should have a pre-prod / QA / SVT environment that will have same setup as intended in Prod, and you do satisfactory load / performance / failover testing.
MQ Client apps should preferrably connect to the most local qmgr (in the same data center) for best performance and reliability. |
Glenn, if the apps don't connect to all of its available qmgrs(to put), would't it cause throughput issues ? and what happens to the msgs when a app connecting to only 1 qmgr(to get) goes down? |
I said preferrably. If the most local qmgr is not available, it should try the next one (in the CCDT or whatever). However, some apps don't have the luxury of being portable across multiple hosting qmgrs (eg. MFT agents with client conns).
If a MQ client app runs on thousands of servers over a wide geographic area (think of a national retail chain), it makes sense to regionalize the connections into more than one qmgr.
_________________
Glenn |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
