Author |
Message
|
EB |
Posted: Wed Nov 16, 2005 12:06 am Post subject: Applying maintenance on MQ cluster |
|
|
 Acolyte
Joined: 19 Mar 2004 Posts: 70
|
Hi
We have 2 clusters (red and green) where 2 application qmgrs run in green and 2 application qmgrs run in red on MQ v 5.3. We also have 2 QMGRs in a bridge between clusters, they are repositories for both clusters. We want apply CSD11. My question is should I start applying maintenance on application qmgrs or repositories? Or does this not matter?
Any other considerations?
Regards
EB |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Nov 16, 2005 3:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
It's always better to start with FRs.
There may not be any particular driving need, but it's always just a little bit safer.' _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
EB |
Posted: Wed Nov 16, 2005 4:38 am Post subject: |
|
|
 Acolyte
Joined: 19 Mar 2004 Posts: 70
|
Thanks alot for the advice, I will start with the full repositories.
Regards
EB |
|
Back to top |
|
 |
EB |
Posted: Thu Nov 17, 2005 10:15 pm Post subject: Maintenance plan |
|
|
 Acolyte
Joined: 19 Mar 2004 Posts: 70
|
Hi again
I have the following plan for apllying maintenance to the infrastructure described above.
-Start with one of the full repositories
-suspend qmgr from both clusters (should I use mode(Force) here?)
-Check that suspension is in effekt
-stop qmgr
-apply CSD11
-restart QMGR if nescessary
-resume qmgr in both clusters
-check that QMGR is resumed in clusters
-repeat action for the other FR.
repeat action for the application qmgrs in their respective clusters.
I would like any comments on this method, have I overlooked any considerations or actions that should be done?
Should I put in tests after each upgrade although not all qmgrs are upgraded?
Any advice is greatly appreciated.
Regards
EB |
|
Back to top |
|
 |
EB |
Posted: Fri Nov 18, 2005 12:01 am Post subject: |
|
|
 Acolyte
Joined: 19 Mar 2004 Posts: 70
|
Hi
If you check the cluster manual it states that the qmgr MUST be suspended from the cluster while applying maintenance, if the qngr hosts queues.
Regards
EB |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Nov 18, 2005 6:06 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
The reason for suspending the QM before ending it so you can start maintenance is so that if there are any in flight MQ messages on that QM they will be processed, while at the same time telling the rest of the cluster to stop sending all optional work to it. The theory is that if you wait a few minutes after the suspend, you can be resonably sure there are no more messages in the system looking for this QM, or on this QM in process.
Of course, you can't be 100% sure now can you? Wait 5 minutes after the suspend, and whose to say some process out there doesn't take 6 minutes to process a request that came from this QM and now the reply is stuck coming back to it anyway because you just shut it down?
With that in mind, I don't bother with SUSPEND. I just go ahead and FORCE STOP the QM's CLUSRCVRs, which immediatly stops all new work from coming in, wait for a few seconds to allow all in process work to finish on the QM, and then end the QM. After restarting the QM, the channels are still STOPPED, so I have control as to when any messages start arriving because I have control over starting those channels. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|