[jira] [Commented] (IGNITE-20424) Slow thin client connection can lead to consuming of huge amount of heap

["Ignite TC Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-20424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774871#comment-17774871 ] 

Ignite TC Bot commented on IGNITE-20424:
----------------------------------------

{panel:title=Branch: [pull/10980/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10980/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Basic 1{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=7559332]]
* {color:#013220}IgniteBasicTestSuite: ClientSessionOutboundQueueLimitTest.testClientSessionOutboundQueueLimit - PASSED{color}

{panel}
[TeamCity *--> Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7559440&buildTypeId=IgniteTests24Java8_RunAll]

> Slow thin client 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
>            Assignee: Mikhail Petrov
>            Priority: Major
>              Labels: ise
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> All messages designated for the thin client are accumulated in the selector queue GridSelectorNioSessionImpl#queue before they are sent. Note that  GridSelectorNioSessionImpl#queue for the Ignite Thin Client currently is unbound. If the thin client connection is slow and a huge number of heavy messages are about to send to the thin client, 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.
> Currently, two mechanisms related to the described problem have already been implemented:
> 1. GridNioServer.Builder#messageQueueSizeListener is used to limit the message queue size for Ignite Thick clients - if the message queue size limit is exceeded, the client node will be forced to leave the cluster.
> 2. GridNioServer.Builder#sendQueueLimit is used to block a thread that sends a message if the message queue size limit is exceeded. Currently is used with Thick Clients and Ignite REST clients.



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