You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every day (at exact the same time), my logstash stalls and doesnt parse any events anymore.
Stack dump shows the input queue is full and the xml filter is stuck in processing.
logstash.err shows a nice error, on exact the moment the processing stops:
Note: logstash ran fine for a day with that xpath and after restarting the service, it continues to.
I know, this is a weird condition, and it might be a bug in nokogiri itself. Though I think the product would be better if we work around this by adding a catch to the xpath evaluation.
I made a change for this issue and im currently testing it, see: hp197/logstash-filter-xml@55f5783
When it works, i'll open up a pull request.
Cheers,
The text was updated successfully, but these errors were encountered:
I can confirm that the workaround works and logstash havent crashed anymore for several weeks. Though it still is a nasty hack and doesnt resolve the original problem.
Hi,
Every day (at exact the same time), my logstash stalls and doesnt parse any events anymore.
Stack dump shows the input queue is full and the xml filter is stuck in processing.
logstash.err shows a nice error, on exact the moment the processing stops:
Note: logstash ran fine for a day with that xpath and after restarting the service, it continues to.
I know, this is a weird condition, and it might be a bug in nokogiri itself. Though I think the product would be better if we work around this by adding a catch to the xpath evaluation.
I made a change for this issue and im currently testing it, see: hp197/logstash-filter-xml@55f5783
When it works, i'll open up a pull request.
Cheers,
The text was updated successfully, but these errors were encountered: