| Author |
Message
|
| mvarghese |
 Posted: Fri Jun 15, 2007 6:28 pm Post subject: What are the normal problems can come cross for a MQ Cluster |
 |
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
Is any one can give a list of major problems can come across in a MQ Cluster Environment..Ley say..3 Cluster set up with 4-5 QMGRs each.
I am expecting some thing like..few problems which are normal in Clusters...and few minor level issues and these few are major level stuffs...Don't say QMGR not running or channels not running or check error log file...any thing other than this:)..it will be useful.
_________________
Jain Varghese |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jun 15, 2007 7:33 pm Post subject: Re: What are the normal problems can come cross for a MQ Clu |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mvarghese wrote: |
Is any one can give a list of major problems can come across in a MQ Cluster Environment..Ley say..3 Cluster set up with 4-5 QMGRs each.
I am expecting some thing like..few problems which are normal in Clusters...and few minor level issues and these few are major level stuffs...Don't say QMGR not running or channels not running or check error log file...any thing other than this:)..it will be useful. |
How about queue full -- back up on SYSTEM.CLUSTER.TRANSMIT.QUEUE -- and a general slowdown of all communications in the cluster....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mvarghese |
| Posted: Sat Jun 16, 2007 8:08 pm Post subject: |
|
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
Thanks fjb_saper, any body have any other points.
_________________
Jain Varghese |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Jun 17, 2007 1:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Not so much with the cluster per se, but with applications. Workload balancing eleiminated by BIND_ON_OPEN because of message affinity, badly routed reply messages, that sort of thing.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Jun 17, 2007 10:38 am Post subject: |
|
|
Guest
|
Most cluster problems seem to fall into three broad categories:
1. bad cluster architecture/design - not understanding what problem/issue you are attempting to resolve by using clusters;
2. 'bad' cluster object definitions;
3. sys admins not following the step-by-step procedures in the MQ V6 Queue Manager Clusters manual to implement clusters, manage clusters, and resolve the bad definitions |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jun 17, 2007 12:46 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
My worst cluster "Nightmare" is another admin just copying the qmgr definitions (MS03) and loading it unto a new cluster qmgr (add load balancing power) but forgetting to delete the cluster receiver / cluster sender channels before loading the definitions...
My word of advice:
- always delete existing cluster sender /cluster receiver channels before loading a new qmgr. (except the system ones of course)
- Ensure that the new qmgr name is unique in the cluster
- Manually define the cluster receiver
- Check that the cluster receiver is adequate for the qmgr it is intended for
- suspend the qmgr from the cluster
- create the cluster sender to a full repository (joining the cluster)
- create any subscription that are cluster dependant if this is a broker qmgr
i.e. subscription qmgr = clusteralias, subscription queue = cluster queue
This allows load balancing of subscriptions
- If all cluster attributes have been verified and right resume the qmgr to the cluster... (start load balancing)
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mvarghese |
| Posted: Mon Jun 18, 2007 8:28 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
Thanks faber, Bruce & Victor.
_________________
Jain Varghese |
|
| Back to top |
|
|
|
|
