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 » General IBM MQ Support » Default Algorithm used by MQ for Clustering

Post new topic  Reply to topic
 Default Algorithm used by MQ for Clustering « View previous topic :: View next topic » 
Author Message
John_peter
PostPosted: Tue Jun 29, 2004 9:27 pm    Post subject: Default Algorithm used by MQ for Clustering Reply with quote

Novice

Joined: 10 May 2004
Posts: 22

On what basis is the queue manager's queue selected during WLoad balancing(default)
The q owned by the queue manager that it sent to least recently

queue manager on the fastest channel(is it based on NETPRTY)??

queue manager that it sent to most recently

queue manager that is receiving the least number of messages
Back to top
View user's profile Send private message
kspranava
PostPosted: Tue Jun 29, 2004 10:49 pm    Post subject: Reply with quote

Centurion

Joined: 27 Apr 2003
Posts: 124

Yes, it is a combination of all.

Below is the round robin algorithm which WebSphere MQ uses by default.
Algorithm: The steps in choosing a destination for a message:
1. If a queue name is specified, eliminate queues that are not PUT enabled.
Eliminate remote instances of queues that do not share a cluster with the local
queue manager.
Eliminate remote CLUSRCVR channels that are not in the same cluster as the
queue.
2. If a queue manager name is specified, eliminate queue manager alias’ that are
not PUT enabled.
Eliminate remote CLUSRCVR channels that are not in the same cluster as the
local queue manager.
3. If the result above contains the local instance of the queue, choose it.
4. If the message is a cluster PCF message, eliminate any queue manager you
have already sent a publication or subscription to.
5. If only remote instances of a queue remains, choose Resumed queue managers
over Suspended ones.
6. If more than one remote instance of a queue remains, include all
MQCHS_INACTIVE and MQCHS_RUNNING channels.
7. If less than one remote instance of a queue remains, include all
MQCHS_BINDING, MQCHS_INITIALIZING, MQCHS_STARTING, and
MQCHS_STOPPING channels.
8. If less than one remote instance of a queue remains, include all
MQCHS_RETRYING channels.
9. If less than one remote instance of a queue remains, include all
MQCHS_REQUESTING, MQCHS_PAUSED and MQCHS_STOPPED channels.
10. If more than one remote instance of a queue remains and the message is a
cluster PCF message, choose locally defined CLUSSDR channels.
11. If more than one remote instance of a queue remains to any queue manager,
choose channels with the highest NETPRTY to each queue manager.
12. If more than one remote instance of a queue remains, choose the least recently
used channel.

(From redbook for clustering.)
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 » General IBM MQ Support » Default Algorithm used by MQ for 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.