| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Log Size Calculations |
« View previous topic :: View next topic » |
| Author |
Message
|
| rammer |
 Posted: Wed Aug 11, 2004 2:42 am Post subject: Log Size Calculations |
 |
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
Hi
Does anybody know if there are any tools (except a calculator) that will work out the desired number of logs and what size they should be created at?
I have read up the section on logs in the Admin guide but am just wandering if there was a tool that would help advise me, so ruling out me making any mistakes on my calculations.
Scenario that I have is:
Distributed solution using Windows 2000 Servers at either end of the chain with a Unix hub in the middle where message are routed via.
A > HUB > B
Messages are to be persistent and the data will be on average 900 bytes
Volume is for 1.5 million message's per day to be routed from A to B via the hub.
Version is MQ5.3 on both platforms, using circular logging.
Thanks in advance |
|
| Back to top |
|
 |
| PGoodhart |
| Posted: Wed Aug 11, 2004 4:20 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
I don't know of any tools other then the formula in the manuals. Just so you know, since it isn't clear in the manuals, by using circular logging and persistent messages, you are limiting the maximum size of the message you can handle. I had an instance where the logs were set up using the defaults on a windows machine and then someone sent a message that was larger then the entire log space. Bad things followed...
So in addition to the formula remember that the entire log space will become the maximum message size that you can handle.
Previous posts have suggested that you make the log space as big as possible, limited basically by the available free space on the drive. I can't actually disagree with that on a dedicated system with big disks.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 11, 2004 5:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
In addition to single messages that are too big for small logs, you have to also consider channel batch sizes if you want to bother with calculating the log space you will use.
I have run into situations where channels failed because the logs on the receiving queue manager were too small for the batch size of the sending channel.
So remember to consider either changing the channel batch size on all your channels, or make your log size big enough to handle a single channel batch.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 11, 2004 11:44 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Depending on slow running/fast running transactions you should allow for more than 2 secondary files. The default is 3 primary and 2 secondaries. With long running transactions this may not be enough. Set your secondaries to 20. It doesn't eat any space when unused and gets cleaned up automatically fast enough.
Remember that you should not run in a prod environment with circular logging. (See IBM red book on disaster / recovery for MQ).
Enjoy |
|
| 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
|
|
|
|
