Does logstash http output plugin has back pressure?

[Dileep_Kumar_Dora]

What happens to events that are not processed by any output

I'm wondering what happens to events that are not written by any output plugin? Reason why I'm asking is that I have a logstash instance running for a couple of days and for no reason (no increased load) it dies with an out of memory error (Java Heap). Now the only reason I could see for that (apart from a memory leak) is that I'm not explicitly discarding (drop filter) events and only writing specific ones to an output ( i do have a if clause in my output section). Would logstash keep them s…

In the above discussion it's mentioned as

Each output has its own retry mechanism - if an event is in an outputs retry queue then the event is still referenced and the JVM does not garbage collect it.

Outputs like elasticsearch will not accepts new events while the are events in the retry queue. This has a back-pressure effect that pushes back all the way to the inputs - they stop accepting new events from upstream.

When I'm working with http output plugin it's not handling backpressure properly. Can someone help with this?

Thanks,
Dileep.