| Author |
Message
|
| KIT_INC |
 Posted: Mon Jun 26, 2017 11:39 am Post subject: Qmgr restart time long |
 |
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
We are running MQ V8 on Linux. QM1 is a MI Qmgr.
Our last failover restart of the Qmgr took almost an hour.
The last log in AMQERR01.LOG shows
AMQ7229: 2818260 log records accessed on queue manager 'QMCGWPR1' during the log replay phase.
QM1 is a MI Qmgr and its log config is
Log:
LogPrimaryFiles=30
LogSecondaryFiles=5
LogFilePages=65535
LogType=CIRCULAR
LogBufferPages=0
LogPath=/remote-var/mqm/log/QM1/
LogWriteIntegrity=TripleWrite
This Qmgr is used as a gateway on a big cluster and has no applications running. (i.e. all processes are MQ processes and mostly channel related). There could be a few hundred cluster channel running at any point in time. I do not expect there is any long running transaction. The channel batch size is 50 and all persistent messages.
I am just wondering why it has to access almost 3 million record to restart.
Where should I start to look ? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Mon Jun 26, 2017 4:43 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
What command did you use to shut the qmgr down?
_________________
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 |
|
|
| gbaddeley |
| Posted: Mon Jun 26, 2017 4:55 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Quote: |
| I am just wondering why it has to access almost 3 million record to restart. Where should I start to look ? |
Look at the curdepth of all the local queues. Look at persistent messages on these queues.
_________________
Glenn |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jun 26, 2017 5:09 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Check your Current and Saved Channel Statuses for any In Doubts.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Jun 27, 2017 12:55 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
And if using large persistent messages it's a good idea to keep the batch size down low rather than leave it at the default.
_________________
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 |
|
|
| Andyh |
| Posted: Tue Jun 27, 2017 1:55 am Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 239
|
By defining a log with 35 extents, each of 256MB you've allowed the queue manager to need to replay up to almost 9GB at QM restart.
It would be unusual for the queue manager to need to replay more than about 50,000 log records and so either you've got HUGE transactions (your append suggests otherwise), or the checkpoint process in the previously active queue manager had failed in some manner.
Were any FDC's reported on the old active QMgr, in particular any FDC's from either amqzmuc0 or amqzxma0 ?
Have you raised a PMR ? |
|
| Back to top |
|
|
|
|
