| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Maximum Log File Size |
« View previous topic :: View next topic » |
| Author |
Message
|
| nik_shaw |
 Posted: Wed Jul 24, 2002 6:24 am Post subject: Maximum Log File Size |
 |
|
Novice
Joined: 17 Jan 2002
Posts: 11
Location: London
|
According to the dialogue boxes when creating a new Queue Manager, the following are the maximum allowable entries under NT :
Log File Size (x4KB) 4095
Log Primary Files 62
Log Secondary Files 61
This gives a theoretical maximum log size of just under 2GB. Does anyone know of a reason not to do this (Disk Space is not a problem)? Is there any performance related issues in doing this? Assuming use of persistent messages in certain scenarios up to ~30MB. Though non-persistent messages will also using this Queue Manager. |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Wed Jul 24, 2002 6:32 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well the issues I can think of:
1) Backup/Restore the system will take longer
2) Qmgr restarts from a crash may take longer (Iam not sure how much)
3) Iam not sure how NT handles memory but it could take more ram to
have the bigger log files open
None of these however are show stoppers. Try it and see.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| bduncan |
| Posted: Wed Jul 24, 2002 7:40 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Another problem is that with so many secondary log files (which don't get created when you set the queue manager up) you run the risk of filling the partition when the secondaries do get created, which could be months or years after you created the queue manager, during which time other files/data have been stored on the partition because greedy sys admins see all that empty space 
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| nik_shaw |
| Posted: Thu Jul 25, 2002 1:42 am Post subject: |
|
|
Novice
Joined: 17 Jan 2002
Posts: 11
Location: London
|
Thanks for the advice guys, so basically as long as we have dedicated disk space (2Gb is nothing these days) and our other resources are able to cope ie Processor / Memory / Network, there is no real downside to maxing out the available log space.
The main reason behind this is that we may have a lot of messages that we can't afford to lose at any point in the system ( which is totally asynchronous), and also many different applications could be sending different messages over it, so we have no idea on max message sizes or frequencies at the moment.
I know it could be considered overkill, but until there is a way of dynamically changing the log files then we may have no other option.
I take it the same sizes exist on other platforms such as Solaris?
thanks
Nik |
|
| Back to top |
|
|
| mrlinux |
| Posted: Thu Jul 25, 2002 3:25 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Yes, my previous assignment we were using HPUX and we had avg around 750,000 messages a day and peaks around 900,000. We set the logs to there maxium size we had some issues with a queue manager crashing every couple of months when we were at v5.0,v5.1 but after that
the problem disappeared.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| 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
|
|
|
|
