[jira] [Assigned] (IGNITE-11966) Using AdaptiveLoadBalancingSpi without IgniteConfiguration.setIncludeEventTypes(EventType.EVT_TASK_FINISHED, EventType.EVT_TASK_FAILED) leads to memory leak

["Ivan Bessonov (JIRA)" <ji...@apache.org>]

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

Ivan Bessonov reassigned IGNITE-11966:
--------------------------------------

    Assignee: Ivan Bessonov

> Using AdaptiveLoadBalancingSpi without IgniteConfiguration.setIncludeEventTypes(EventType.EVT_TASK_FINISHED,  EventType.EVT_TASK_FAILED) leads to memory leak
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11966
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11966
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.7.5
>            Reporter: Andrey Aleksandrov
>            Assignee: Ivan Bessonov
>            Priority: Major
>             Fix For: 2.8
>
>         Attachments: Top_Consumers.zip
>
>
> You can use in debug mode any of tests related to AdaptiveLoadBalancingSpi like GridAdaptiveLoadBalancingSpiSelfTest.
> In case if you don't subscribe on EventType.EVT_TASK_FINISHED,  EventType.EVT_TASK_FAILED then next code will be never called:
> case EVT_TASK_FINISHED:
> case EVT_TASK_FAILED: {
>  TaskEvent taskEvt = (TaskEvent)evt;
>  taskTops.remove(taskEvt.taskSessionId()); //this
> As a result, you will see the growth of memory usage.
> [^Top_Consumers.zip]
>  if (log.isDebugEnabled())
>  log.debug("Removed task topology from topology cache for session: " +
>  taskEvt.taskSessionId());
>  break;
> }



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)