> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of [email protected] > Sent: Thursday, May 28, 2009 6:07 PM > To: rsyslog-users > Subject: Re: [rsyslog] disk-assisted queue - feedback requested > > On Thu, 28 May 2009, Rainer Gerhards wrote: > > > I think what I would need some time soon is someone looking at the new > > engine. I tried hard to create test cases, but without some feedback from > > practice, it is really hard. If that helps, I can create a tarball ;) > > at this point I don't know what the status of things are. the last I > remember seeing was that things shifted into the 'very unstable, > experimenters only' stage, then you said that the tests completed, but > there was still more to do before it could be considered stable. > > is it now to the point where you think it's pretty stable (few or no known > problems, but needs testers to find the unknown problems)?
Well, I've ironed out many problems, but I think that still a number of them remain (I may be wrong), but I am running out of ideas of what to test. What really hurt was the ultra-reliable queue mode, it created lots of problems inside the queue engine. > I've also lost track of what has gone into things at this point, so I'm > not sure what I would need to test (let alone the new config variables I > would need to know about to do the testing) At this point, I would be interested in feedback a) if existing real-world configurations continue to work b) on the performance of the new engine So it does not even involve any new config variables. If you look at the testbench, I have really added lots of automated tests, but that is different from practice. My own lab also has only limited exposure. So, yes, the code probably is still highly experimental, but I am running out of ideas on how to get it better without any real-world feedback. There are some bits missing, but I'd prefer to see that what currently is there is decently stable before I work on these (minor) issues. They should not hurt normal operations. So if you or someone else could provide some feedback, that would be very useful. I can't outrule that it breaks immediately, but in my lab it doesn't do ;) The code is currently held in the v5-devel git branch. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
