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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.5
• Fix Version/s: 2.8
• Ignite Flags: Docs Required
• Assignee: Ivan Bessonov
• Reporter: Andrei Aleksandrov
• Created: 04/Jul/19 15:31
• Updated: 17/Jul/19 12:12
• Resolved: 17/Jul/19 12:09

Description

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; }

Issue Links

• links to: GitHub Pull Request #6690