You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Kovalenko (JIRA)" <ji...@apache.org> on 2019/04/18 14:48:00 UTC

[jira] [Commented] (IGNITE-11767) GridDhtPartitionsFullMessage retains huge maps on heap ion exchange history

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

Pavel Kovalenko commented on IGNITE-11767:
------------------------------------------

[~ilyak] Overall approach to solving the problem looks good. Partition sizes map in FullMessage is read only once during topology update, so it's safe to keep it in the serialized format every time.

> GridDhtPartitionsFullMessage retains huge maps on heap ion exchange history
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-11767
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11767
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.7
>            Reporter: Ilya Kasnacheev
>            Assignee: Ilya Kasnacheev
>            Priority: Blocker
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> ExchangeHistory keeps a FinishState for every topology version.
> FinishState contains msg, which contains at least two huge maps:
> partCntrs2 and partsSizesBytes.
> We should probably strip msg, removing those two data structures before putting msg in exchFuts linked list to be stowed away.



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