Posted: Sun Sep 20, 2009 10:06 am Post subject: MQ Cluster with 4000 publishers
Acolyte
Joined: 29 Nov 2004 Posts: 67 Location: London
I am designing an MQ cluster with 4000 JMS publishers with each sending messages at 1msg/sec. It is not an issue to manage the configuration on the endpoints and hence I am thinking of sending a server dns list to the endpoints so that they can randomly pick one from the list and upon initial connection failure, do a round-robin loadbalancing.
The primary requirement is that the server should scale horizontally and that client shoud automatically fail over.
Now my questions are :-
1) Is there a better load-balancing technique?
2) Can MQ Server handle around 1000 parallel tcp/ip connections with a throughput of 1000 persistent messages/sec? I have seen performance reports for IBM support packs but havent' seen any with such large no of publishers.
Posted: Sun Sep 20, 2009 10:32 am Post subject: Re: MQ Cluster with 4000 publishers
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
sieijish wrote:
I am thinking of sending a server dns list to the endpoints so that they can randomly pick one from the list and upon initial connection failure, do a round-robin loadbalancing.
Why not send a CCDT to each of the endpoints so they can use the method provided by WMQ to reconnect to a different queue manager in the event of failure? Rather than rolling your own with a DNS table?
Also why using a WMQ cluster, then try to load balance via the endpoints? Why not use the load balancing provided by WMQ?
sieijish wrote:
Now my questions are :-
1) Is there a better load-balancing technique?
See my responses above?
sieijish wrote:
2) Can MQ Server handle around 1000 parallel tcp/ip connections with a throughput of 1000 persistent messages/sec? I have seen performance reports for IBM support packs but havent' seen any with such large no of publishers.
The better question is can your hardware handle it? The software certainly can if there's enough memory particually & other resources generally.
Another good question is what happens when one of the queue managers fails and the app randomly picks (I use your term) another one, and adds it's message load to the one designated to the server. _________________ Honesty is the best policy.
Insanity is the best defence.
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