On Fri, 18 Mar 2016, David Lang wrote:
Figuring that there is a reasonable chance that these problems are due to
the mixing of versions, I compiled from today's git tree and deployed that
to a server that's receiving a flood of logs from queues that are flushing
to it. When I deployed the new version, the throughput dropped noticably
(~30% drop from handling ~300K messages/min to handling 200K messages/min)
One thing that triggers my mind is the change of hash function. In
8.17, we use a different hash function inside libfastjson. This has
prooven to be much faster in experiments we carried out, but maybe
it's not the case for you. You can comment out line 1640
https://github.com/rsyslog/rsyslog/blob/master/tools/rsyslogd.c#L1640
here and see what happens.
I'll try to give that a try, but may not get a chance before monday.
By the way, the libfastjson version number is still 0.9.2 in the git tree,
you missed bumping it to 0.9.3 after the release.
something triggered a restart of rsyslog and it started running with the plain
0.9.2 libjsonfast, it appears that that is enough to trigger the memory leak.
I'm not sure what triggered the restart
installing the 0.9.2-20160327* version again seems to have caused it to not
leak.
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.
