[jira] [Updated] (IGNITE-20424) [Thin clients] Slow thin clients connection can lead to consuming of huge amount of heap

["Mikhail Petrov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-20424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Petrov updated IGNITE-20424:
------------------------------------
    Summary: [Thin clients] Slow thin clients connection can lead to consuming of huge amount of heap   (was: [Thin clients] Slow thin clients connection can lead to huge amount heap consuming)

> [Thin clients] Slow thin clients connection can lead to consuming of huge amount of heap 
> -----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-20424
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20424
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Mikhail Petrov
>            Priority: Major
>              Labels: ise
>
> All messages designated for the thin client are accumulated in the selector queue GridSelectorNioSessionImpl#queue before they are sent. Note that  GridSelectorNioSessionImpl#queue  is unbound. If the thin client connection is slow and a huge number of messages with a large weight will be sent to it, GridSelectorNioSessionImpl#queue growing size can lead to OOM.
> See 
> 1. https://issues.apache.org/jira/browse/IGNITE-20327  
> 2. https://github.com/apache/ignite/issues/10559
> We need to investigate mechanisms to limit the thin client message queue size.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)