[rabbitmq-discuss] Running StressPersister.java client against RabbitMQ and finding the stress_persister.log file is being "beaten to death"
johndapps at gmail.com
Tue Jan 19 14:36:29 GMT 2010
Oh well, please excuse a beginner and someone who asks first and reads
Your assumption is correct. I shall now go and read...
Should we (tongue in cheek) have a crack at it with the new persister?
Thank you, John
On Tue, Jan 19, 2010 at 15:18, Matthew Sackman <matthew at lshift.net> wrote:
> On Tue, Jan 19, 2010 at 02:03:22PM +0000, Matthew Sackman wrote:
> > On Tue, Jan 19, 2010 at 10:22:29AM +0100, John Apps wrote:
> > > What parameters should one tweak in order to reduce the I/O to the log
> > > in the StressPersister test? And others with similar behaviour, of
> > A quick look at the code suggests changing the sample interval with s
> > should do the trick.
> > > The file grows to about 140MB using the default StressPersister
> > > only to be renamed to stress_persister.log.previous and the whole cycle
> > > starts again.
> I've just twigged - you've set the rabbit nodename to stress haven't
> you? Thus the stress_persister.log and stress_persister.log.previous are
> actually the persister files. These are the very files to which the
> (old) persister is writing messages which have to be written to disk.
> There are many issues with the old persister, which have been regularly
> discussed on this list, and many people are using the new persister
> which has been in development for almost a full year now.
> See eg http://old.nabble.com/Re:-Rabbit-MQ-crashing-p27042793.html to
> start with.
> Best wishes,
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
(49) 171 869 1813
Sent from Grassau, Bavaria, Germany
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss