| Author |
Message
|
| skrv |
 Posted: Thu Jul 23, 2015 7:35 am Post subject: Cluster Cleanup Procedure |
 |
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
Hi,
We have MQ at 7.5.0.3 and all are z-linux servers.
We have a cluster by name "DEM" and it has 2 full repositories and 2 partial repositories.
It is no longer needed and we need to retire this cluster. Can some one help us with the clear step by step instructions for decommissioning cluster communication and delete everything related to this cluster?
thanks in advance |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Jul 23, 2015 7:42 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
So you don't want any of the queue managers left?
If so then something like (instead of the big bang, stop everything, delete everything)
remove the PR's from the cluster
stop the PR Queue Managers
delete the PR Queue managers
stop the Other QMGRS
delete the remaining QMGRS
So how would you think it should be done?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| skrv |
| Posted: Thu Jul 23, 2015 8:30 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2012
Posts: 118
|
we are not going to delete the queue managers.
while stopping and deleting the channels, we need to know the specific order like which channel to be altered/stopped/deleted..... first... |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Jul 23, 2015 4:45 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 24, 2015 5:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
0. Remove all queues on the PRs from the cluster.
Just to put on the suspenders. |
|
| Back to top |
|
|
| tczielke |
| Posted: Fri Jul 24, 2015 8:34 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
If you want to completely remove a cluster like CLUS1, you might also have to do a RESET CLUSTER(CLUS1) on the partial repository queue managers after CLUS1 has been removed from them. That was at least my experience.
I followed the manual instructions for removing a cluster and I did see CLUS1 completely check out of the queue manager partial repositories that were holding CLUS1, so I thought I was all set. However, 1-2 days later the partials would start to try and connect back to the full repositories for CLUS1, and I had to do RESET CLUSTER(CLUS1) (or maybe it was a REFRESH CLUSTER) on the partial repositories to get them to stop doing that.
It felt like the song "but the cat came back the very next day . . . "
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 24, 2015 9:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| tczielke wrote: |
If you want to completely remove a cluster like CLUS1, you might also have to do a RESET CLUSTER(CLUS1) on the partial repository queue managers after CLUS1 has been removed from them. That was at least my experience.
I followed the manual instructions for removing a cluster and I did see CLUS1 completely check out of the queue manager partial repositories that were holding CLUS1, so I thought I was all set. However, 1-2 days later the partials would start to try and connect back to the full repositories for CLUS1, and I had to do RESET CLUSTER(CLUS1) (or maybe it was a REFRESH CLUSTER) on the partial repositories to get them to stop doing that.
It felt like the song "but the cat came back the very next day . . . " |
Did you remove the FR's too ?
Did you remove the cluster sdr/receivers on the PRS ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 24, 2015 10:19 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And with V7 & V8 did you remove any other clustered objects like topics? (often forgotten in the list of objects to uncluster....) The clustered channels get removed last from the QMGR... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tczielke |
| Posted: Fri Jul 24, 2015 1:42 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
It has been a few months since I did it, so it is hard for me to remember for sure exactly what I did.
There were no clustered queues or topics on partial repository QM1 when I started. I remember following all the instructions in this doc to remove say partial repository QM1 from CLUS1 -> http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.con.doc/q017520_.htm
When I was done the partial repository on QM1 showed that it was no longer in CLUS1, and the full repositories for QM1 had also dropped QM1 from CLUS1. However, 1-2 days later, QM1 started up a CLUSSDR channel again to the full repositories for CLUS1. I think I had to do a REFRESH CLUSTER(CLUS1) on QM1 to correct this. But it has been a while.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jul 25, 2015 12:18 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| tczielke wrote: |
When I was done the partial repository on QM1 showed that it was no longer in CLUS1, and the full repositories for QM1 had also dropped QM1 from CLUS1. However, 1-2 days later, QM1 started up a CLUSSDR channel again to the full repositories for CLUS1. I think I had to do a REFRESH CLUSTER(CLUS1) on QM1 to correct this. But it has been a while. |
Was that an autodefined one, or a manually defined one? If it was an autodefined one did you open a PMR (because it should not have happened) ...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tczielke |
| Posted: Sat Jul 25, 2015 4:49 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
It was a manually defined CLUSSDR channel to the full repository, but it also had its CLUSTER set to spaces, per that doc. The doc only said to delete the CLUSRCVR channel, so I left the CLUSSDR channel defined. I did not open a PMR. Doing the REFRESH CLUSTER on the PR qmgr corrected the problem of the CLUSSDR channel starting back up for the FR.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jul 25, 2015 6:38 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| tczielke wrote: |
| It was a manually defined CLUSSDR channel to the full repository, but it also had its CLUSTER set to spaces, per that doc. The doc only said to delete the CLUSRCVR channel, so I left the CLUSSDR channel defined. I did not open a PMR. Doing the REFRESH CLUSTER on the PR qmgr corrected the problem of the CLUSSDR channel starting back up for the FR. |
I thought the last step after setting the channel to a blank cluster was to stop the channel, start the channel stop the channel and delete the channel...
I guess we must have skipped the delete the channel part...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Jul 27, 2015 5:53 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| When stopping the cluster channel, choose the "inactive" state and stop the sender (the receiver will automatically stop). |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 27, 2015 7:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| JosephGramig wrote: |
| When stopping the cluster channel, choose the "inactive" state and stop the sender (the receiver will automatically stop). |
This needs a lot more precision... and seems intuitively false...
- Sure I remove all clustered objects
- Make the qmgr a partial if full repository
- change the cluster receiver to cluster(' ') clusnl('')
- bounce the cluster receiver channel (twice) => sure this will stop all the corresponding cluster senders)
- stop the cluster receiver (twice)
- change the cluster sender to cluster('') clusnl('')
- bounce the cluster sender (twice)
- stop the cluster sender (twice if you want to avoid mode (terminate))
- delete the cluster receiver
- delete the cluster sender.
Hope this helps :innocent"
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
