On Thu, 25 Feb 2016, Kane Kim wrote:
Thanks, David, I'll give it a try.
What about TryResume/DoAction question? I changed TryResume to always
return RS_RET_OK and DoAction returns RS_RET_SUSPENDED, I print debug
information in TryResume/DoAction, log one line, DoAction is called once
and not retried after that.
sorry, you're talking at a level that I don't know the details on. You will need
to wait for Rainer and the others from Adiscon to get back (from their posts,
probably about a week)
From Rainer's quick posts, it sounds as if there were some changes in the v8
engine that are causing grief.
In the v7 engine, when you processed a batch of messages, it processed them all
for the first action, then processed them all for the second action, etc. This
ran into grief when you had things where the result of one action would affect
the next (the classic case being a counter that you incriment for each message.
the second action would see the counter being the same for every message in the
batch)
the v8 engine changed this so that all actions are taken for the first message,
then all actions for the second message, etc.
reading between the lines of Rainer's message (and this may be very wrong), it
sounds as if what happens is
start batch, mark messages in the queue as being worked on.
foreach message_in_batch {
foreach action {
evaluate filter for action
apply output template to current variables to create a chunk of output data
}
}
foreach action {
trigger delivery of output data
}
batch finished, mark messages as delivered from queue
and therefor, when you find that you can't deliver the message, you may not know
which message in the batch had the problem, so there's no way to go back.
I may be completely wrong, which is why we need to wait for Rainer to get back
and comment. There should be more than this, because the flow above should be
able to return 'something in this batch failed, try again with a half size
batch' to narrow things down to a particular message that's failing.
sorry I can't be more help.
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.
