On Mon, 1 Oct 2012, Rainer Gerhards wrote:
enabling batching should not change this as rsyslog does not wait for a
batch to be full before processing it, instead the batch is the maximum
number of messages it will pull off the message queue to process at
once.
IIRC, omoracle does it's own kind of batching, so it is disjunkt from
rsyslog batching. Not sure, though.
Ok, that would explain many issues. It makes sense that since omoracle is
older than batching mode it could have not gotten updated to match the
more modern interface. It's a problem though in that it causes this type
of problem.
If omoracle does not work, would it make sense to try omlibdbi? In
theory it should work with oracle, but I have not test environment at
all to try this out.
One problem with omlibdbi is that I believe that it doesn't do any
batching, it also disables all transactions on the database server, so you
end up sacraficing a lot of the reliability that you are probably
expecting to get from using a database in the first place.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
