Implement a strategy to handle OOM in direct memory #475
Commits on Sep 27, 2023
-
Avoid to run Beats parser and Beats protocol handler in separate exec…
…utors group (beatsHandlerExecutorGroup)
-
-
-
-
Update the flow control handler to avoid new reads if the channel bec…
…omes not writable, to excert backpressure to the sender system
-
Separated the logic to drop incoming connections into specific handler
On new channel registration (that correspond to a new client connection), verifies the direct memory stastus to understand if almost the totality max direct memory is reached and also if the majoproity of that space is used by pinned byte buffers. If the codition is verified that means direct memory avvailable is terminating, so no new connection would help in the situation, and the incoming new connections are closed.
-
-
Removed tests using EmbeddedChannel because doesn't manage the writea…
…ble status due to that offload every message to the outbound list
-
-
-
-
Raised up the log level level when dropping connections becuase of th…
…undering and going to OOM condition
-
Better actionable suggestion to user in case of OOM
Co-authored-by: João Duarte <[email protected]>
-
Updated OOMConnectionCloser to monitor the consumption of memory also…
… during the read opeartion and not only on exception
-
Re-introduce the beats handlers worker group to separata the Beats pr…
…otocol processing from the boss group that accepts and listed to new sockets
-
Added feature flag named protect_direct_memory to control the usage o…
…f OOM checking or not. Enabled by default.
-
