|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
RESET CLUSTER against another Full Repository? |
« View previous topic :: View next topic » |
Author |
Message
|
PeterPotkay |
Posted: Wed May 04, 2005 12:12 pm Post subject: RESET CLUSTER against another Full Repository? |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
RESET CLUSTER can only be done from a Full Repository (FR) to boot out a QM from a cluster.
If I have FR1 and FR2 in a cluster, and the server housing FR1 is destroyed, I will need to rebuild FR1. Since the original FR1 was not gracefully removed from the cluster, the cluster will still know about it.
Can I use RESET CLUSTER(*) QMNAME (FR1) ACTION(FORCEREMOVE) QUEUES(YES) from FR2 prior to creating the replacement FR1? Will that keep my cluster working if I ever need to reintroduce the same named Qm into a cluster because the original one was destroyed? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed May 04, 2005 12:21 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Peter,
In the documentation about the Reset cluster you have 2 option
a) by qmgr name
b) by qmgr id
This will allow you to recreate your qmgr and then boot out the old one with the same name but different ID.
Never tried it but that's the theory.  |
|
Back to top |
|
 |
PeterPotkay |
Posted: Wed May 04, 2005 12:23 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Right, but can I do it against another FR? It specifically says you need to run the command FROM a FR, but I want to be clear that I can run it force out a bogus QM in the cluster that was a FR itself before it got destroyed. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed May 04, 2005 12:33 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Only way to know: try it.
I would expect that it is geared specifically towards this purpose whether FR or PR used as target to boot out of the cluster.
There must be cases where the qmgr blows up and there is no way of recovering it. This is why they would have added the Qmgrid option.
 |
|
Back to top |
|
 |
offshore |
Posted: Fri May 13, 2005 5:19 am Post subject: |
|
|
 Master
Joined: 20 Jun 2002 Posts: 222
|
Peter,
Did you try this & did it work? I'm just curious.
I was reasoning and couldn't see why it would not work. If you look at the repository info, the QMID is what shows up over and over.
I don't completely understand who the reset works, but it seems that if you force FR1 out of the cluster, before reintroducing the new FR1 it should work. The magic of the command will get rid of any reference to QM Name FR.
Just my .001.
Later |
|
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
|
|
|
|