| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| what is the max # of qmgrs that can be in one cluster? |
« View previous topic :: View next topic » |
| Author |
Message
|
| upsscs1 |
 Posted: Fri Aug 29, 2003 8:04 am Post subject: what is the max # of qmgrs that can be in one cluster? |
 |
|
Newbie
Joined: 02 Jul 2003
Posts: 3
|
| Does anyone know how many queue managers I can put in one cluster before I start to have problems? (performance, ect..) |
|
| Back to top |
|
 |
| EddieA |
| Posted: Fri Aug 29, 2003 9:25 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
I'm not sure there is any limit.
As far as performance goes, once the Queue Managers know about each other, and the Cluster queues, then the messages only go from the Sending Queue Manager to the Receiving one directly, never multi-hop. MQ will define the channels as needed. So, the perfomance limitations woulod be purely MQ ones, not because of clustering.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Aug 29, 2003 11:23 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The following is based on the clustering session at this year's IBM MQ Conferance:
There are no predefined limits to the size of a cluster. The main thing to consider is the maximum number
channels that will need to connect to your server queue managers (and also to the full repositories). If for
instance, you are hosting cluster queues on a WMQ 5.3 z/OS queue manager, then the maximum number
channels is about 9000. This would give a maximum theoretical cluster size of 4500 queue managers, if ea
queue manager in the cluster had one channel going to the server queue manager and one channel back fr
the server queue manager.
If you require more queue managers than this, there are ways that this can be achieved. For example you
could have more than one backend server and a customized workload balancing exit could be written to
partition the work across the different servers. The internal workload algorithm will always round robin acro
all the servers so they would each need to cope with channels from all the clients. We will look closer at
workload balancing later in the presentation.
One question we are regularly asked is whether it is better to have one large cluster or multiple smaller
clusters. This should be a business decision only. It may be for example that you wish to separate secure
requests coming from branches of the business over channels using SSL from unsecure requests coming
from the internet. Multiple clusters would allow you to achieve this whilst still using the same backend serv
to handle both request types.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
