If a codec exception is not caught within the codec itself, it is caught by the inputworker.
This causes the inputworker to raise an exception and stop running completely.
It can be triggered by using logstash-codec-collectd under high load. Exceptions are raised, but not caught.
I have a patch that solves the problem. The exception is caught and handled just like when an TCP listener dies.
If a codec exception is not caught within the codec itself, it is caught by the inputworker.
This causes the inputworker to raise an exception and stop running completely.
It can be triggered by using logstash-codec-collectd under high load. Exceptions are raised, but not caught.
I have a patch that solves the problem. The exception is caught and handled just like when an TCP listener dies.