Hello, I have noticed an always increasing memory use when using omelasticsearch on rsyslog 7.4.4.
Even once the action queues are full, the ram increases goes on, reaching 30GB in about 10minutes (21M messages enqueued). A valgrind launched with --leak-check=full shows that: > ==56893== 137,545,752 bytes in 898,534 blocks are definitely lost in loss > record 141 of 141 > ==56893== at 0x4C279EE: malloc (vg_replace_malloc.c:270) > ==56893== by 0x5AFE3B9: es_newStr (in /usr/lib64/libestr.so.0.0.0) > ==56893== by 0x5AFE6FE: es_newStrFromCStr (in /usr/lib64/libestr.so.0.0.0) > ==56893== by 0x13EA7D: msgGetMsgVarNew (in /sbin/rsyslogd) > ==56893== by 0x134E40: cnfGetVar (in /sbin/rsyslogd) > ==56893== by 0x12FBD3: cnfexprEval (in /sbin/rsyslogd) > ==56893== by 0x12EE97: ??? (in /sbin/rsyslogd) > ==56893== by 0x12FC03: cnfexprEval (in /sbin/rsyslogd) > ==56893== by 0x12FB58: cnfexprEval (in /sbin/rsyslogd) > ==56893== by 0x12FC83: cnfexprEval (in /sbin/rsyslogd) > ==56893== by 0x13085F: cnfexprEvalBool (in /sbin/rsyslogd) > ==56893== by 0x15156F: ??? (in /sbin/rsyslogd Does any one experienced that before ? I have filed a ticket (http://bugzilla.adiscon.com/show_bug.cgi?id=486) to help adding information about the issue. -- Grégoire _______________________________________________ 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.
