ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » Large non-critical messages and Clustering

Post new topic  Reply to topic
 Large non-critical messages and Clustering « View previous topic :: View next topic » 
Author Message
warrenJ
PostPosted: Wed Mar 09, 2005 10:59 pm    Post subject: Large non-critical messages and Clustering Reply with quote

Apprentice

Joined: 11 Jan 2004
Posts: 29
Location: AUSTRALIA

We have an upcoming development where an application will be sending messages up to 4Mb - they are non time crticial as compared to our various real time systems. My concern is that if we use Clustered queues all the messages will be going via the STSTEM.CLUSTER.TRANSMIT.QUEUEs and the large messages may impact on the performance of the all the other traffic. Our preference for Clustering is that we can use it to load balance across several servers.

Is it possible for Clustering to use another XMITQ ? or is my only option to go back to using dedicated QRemotes with their own specific channels.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Fri Mar 11, 2005 4:42 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Use stacked clusters.

Consider a cluster of 3 QMs :FR1, FR2 and PR3.

First put them on Cluster1, so define CLUSRCVRs like TO.FR1.CLUSTER1, TO.FR2.CLUSTER1, TO.PR1.CLUSTER1. CLuster these all to CLUSTER1. Do the same for the CLUSSNDRs.

The create the channels again, but for CLUSTER2:TO.FR1.CLUSTER2, TO.FR2.CLUSTER2, TO.PR1.CLUSTER2. CLuster these all to CLUSTER2. Tune these channels for BATCH style activity.

Cretae a Name list called CLUSTERNAMELIST. For the values, fill in CLUSTER1,CLUSTER2.

For the Full Repositirys, use the Repository Namelist attribute and fill in CLUSTERNAMELIST.

For all common queues on the QMs that you want visible to both clusters, use their cluster namelist attribute and fill in CLUSTERNAMELIST. Both clusters will see them.

For queues you want to use only the CLUSTER2 channels, use their CLUSTER attribute and set it to CLUSTER2. These would be all the queues used by a batch transaction.

Every other queue gets CLUSTER1.

Now when there are messages in the S.C.T.Q., the CLUSTER2 channels pull the batch messages, and the CLUSTER1 channels pull everything else. The 2 do not get in each others way.

I did this not for Batch, but for 2 sets of applications: one set needed channels that were set to FAST, the other apps were happy with channels speeds of NORMAL. I stacked the clusters, and it has been working perfectly for 2 years.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sat Mar 12, 2005 5:07 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

But you need to be VERY CAREFUL about creating TOO MANY Clusters, as well.

If you start building one cluster for every application in your enterprise, you will get in trouble down the road.

So go ahead and create stacked clusters for Batch and Normal processing, and maybe even for Fast processing. But don't create one for Monday's processing, Tuesday's processing, etc....

A cluster is a network. Nobody builds new networks for new applications, if they've got one that meets the needs already.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
warrenJ
PostPosted: Sun Mar 13, 2005 2:01 pm    Post subject: Reply with quote

Apprentice

Joined: 11 Jan 2004
Posts: 29
Location: AUSTRALIA

Thanks for the replies - good to get other view points.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sun Mar 13, 2005 2:20 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

How about using message priority ?
Back to top
View user's profile Send private message Send e-mail
warrenJ
PostPosted: Sun Mar 13, 2005 7:11 pm    Post subject: Reply with quote

Apprentice

Joined: 11 Jan 2004
Posts: 29
Location: AUSTRALIA

The problem I see with Message Priority is that the MCA could start to send a large message and then some real time (small) messages arrive and they will have to wait until the large message is processed.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » Large non-critical messages and Clustering
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.