| Author |
Message
|
| student |
 Posted: Mon Dec 06, 2010 7:13 am Post subject: shutdown/restart of server having cluster queue manager |
 |
|
Apprentice
Joined: 17 Mar 2009
Posts: 31
Location: UK
|
I have query regarding a cluster setup in production.
The setup is as below 4 qgmrs in a cluster named cluster1.
Server 1
clusqmgr A1
clusqmgr B1 (Repository)
Server 2
clusqmgr A2
clusqmgr B2 (Repository)
Server1 has to be shutdown and moved from one room one to another. Then server1 will be started with in 2-3 hours. What are steps/precautions should we follow in this case from MQ side. please advice |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Mon Dec 06, 2010 7:25 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
suspend it?
did you check the cluster manual (maintaining a queuemanager)?
_________________
Regards, Butcher |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Dec 06, 2010 7:29 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
If it is merely a change of room and nothing else, then nothing need be done other than to stop each queue manager properly, i.e. end normally. For such a small amount of time there should be little if any impact, but if it's worrying you:
1. Ensure all applications that 'send' messages are stopped;
2. Ensure all application queues are emptied, then stop those applications;
3. End the queue managers;
4. Move the server;
5. Restart the server and queue managers;
6. Confidence test.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| student |
| Posted: Mon Dec 06, 2010 7:56 am Post subject: |
|
|
Apprentice
Joined: 17 Mar 2009
Posts: 31
Location: UK
|
| Thanks every one. Just one confrimation, is suspending of queue qmgrs necessary before bringing down the qmgrs? Then resume queuemanager after restart |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Dec 06, 2010 8:03 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
In this case, as it is a 'short' outage, I say not necessary. Make sure you bring up the FR first though, and establish that both FR's have recovered channels to each other.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Dec 06, 2010 9:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| student wrote: |
| Thanks every one. Just one confirmation, is suspending of queue qmgrs necessary before bringing down the qmgrs? Then resume queuemanager after restart |
For this "short" an outage it may not be necessary, however it makes for a much cleaner shutdown and allows you to "force" the messages to go to the unsuspended qmgr (the assumption here is that A1=A2 and B1=B2).
While the qmgr is suspended from the cluster the apps can empty the queues. You can then shutdown the qmgrs and finally the box.
Don't forget to resume the qmgr to the cluster once it is back up.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Dec 06, 2010 11:13 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Read about the SUSPEND command in the WMQ Clusters manual. What does it do exactly?
From what you read, do you believe it is necessary to issue the SUSPEND command?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 07, 2010 9:39 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bruce2359 wrote: |
Read about the SUSPEND command in the WMQ Clusters manual. What does it do exactly?
From what you read, do you believe it is necessary to issue the SUSPEND command? |
As the manual says: a qmgr that has been suspended from the MQ cluster will no longer take traffic for it's cluster queues providing they are not the only instance of the cluster queue in the cluster.
So in brief, suspending the qmgr from the cluster allows you to "stop" the incoming traffic while the applications service the queues to empty them.
Imagine a cluster with 3 qmgrs: a gateway server (G) and 2 app servers A and B. Qmgrs A and B are identical clones. Putting applications connect to G. If I need to maintain A, I can suspend it and all traffic will go to B instead of being load balanced between A and B.
The "hard" form of the suspend command stops the cluster receiver channel.
Hope this is clear enough.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Dec 07, 2010 9:46 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
And... to refer to the WMQ Clusters manual once again...
You should allow all applications using the cluster queue(s) to end; then put-inhibit the queues to ensure no new application MQOPENs find the about-to-be-suspended qmgr queues; then (when all apps have ended) do the SUSPEND.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Dec 08, 2010 1:16 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bruce2359 wrote: |
And... to refer to the WMQ Clusters manual once again...
You should allow all applications using the cluster queue(s) to end; then put-inhibit the queues to ensure no new application MQOPENs find the about-to-be-suspended qmgr queues; then (when all apps have ended) do the SUSPEND. |
Remember to distinguish between applications connected locally and load balanced applications that cannot be disrupted. The suspend command will allow you to exclude from load balancing, at qmgr level, if the putting app truly opens the queue in not fixed mode. The put inhibit would just send messages to the DLQ before informing the putting application to no longer use the queue instance.
This is why my rule is first suspend, then put inhibit (if still necessary). But remember: I have no applications putting locally... and they all use bind not fixed...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
