[jira] [Commented] (IGNITE-11058) Possible OOM due to large discard queue in TcpDiscoverySpi

[Ignite TC Bot (JIRA)]

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

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

{panel:title=--> Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Continuous Query 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3152827]]
* IgniteCacheQuerySelfTestSuite4: 
CacheContinuousQueryFailoverMvccTxSelfTest.testMultiThreadedFailover - 0,0% 
fails in last 341 master runs.

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

> Possible OOM due to large discard queue in TcpDiscoverySpi
> ----------------------------------------------------------
>
>                 Key: IGNITE-11058
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11058
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexei Scherbakov
>            Assignee: Sergey Antonov
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently it's necessary to store every ensured (marked with 
> TcpDiscoveryEnsureDelivery annotation) in pending message queue until it's 
> discarded from coordinator for implementing guaranteed delivery, otherwise if 
> subsequent nodes will fail while forwarding message the guarantee couldn't be 
> fulfilled.
> On large topologies with active changes the queue may contain many very large 
> messages causing heap usage bursts and possible OOM.
> Possible solution:
>  # off-load pending messages payload to off-heap or even on disk.
>  # store messages in serialized form for avoiding JVM Object overhead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)