| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CLUSTER |
« View previous topic :: View next topic » |
| Author |
Message
|
| masteringmq |
 Posted: Tue Jan 13, 2009 11:46 pm Post subject: CLUSTER |
 |
|
Master
Joined: 20 Oct 2008
Posts: 200
|
REFRESH CLUSTER(*) REPOS(YES)
- Cluster channel will be stopped
- Remove the cluster queue manager record from the local catch
- Reconnects the manually defined channel to the FR queue manager
- Can only run on partial repositories
REFRESH CLUSTER(*) REPOS(NO)
- Cluster channels will remain running
- Cluster sender channel is used to inform the rest of the cluster that the refresh is completed
- Remove and rebuilt the local catch from the other full repository
- Can run on both full and partial repository
I often use REFRESH CLUSTER(<CLUSNAME>). In which scenario do I use the REFRESH CLUSTER with the option REPOS(NO) and REPOS(YES)?. |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Wed Jan 14, 2009 12:33 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
check thje queue manager clusters manual, Chapter 6. Using WebSphere MQ commands with clusters, there is a good explanation of the refresh cluster command (for MQ V6 it is at page 72, including the differences between repos(no) and repos(yes).
you should take notice of the first sentence of this documentation:
| Quote: |
| You are unlikely to need to use this command, except in exceptional circumstances. |
so maybe you should also check why you have to use that REFRESH CLUSTER command "often". you should not need to do so. Maybe it is a general cluster setup problem that you have.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 14, 2009 12:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Mr Butcher wrote: |
| maybe you should also check why you have to use that REFRESH CLUSTER command "often". you should not need to do so. Maybe it is a general cluster setup problem that you have. |
Issuing the command "just in case" is likely to cause more problems than it solves long term, especially in a cluster of any size. It's certainly a waste of time in a functioning cluster.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
