Stanilovsky Evgeny created IGNITE-14131:
-------------------------------------------
Summary: IgniteCompute tasks with same name, running from one node
and different ClassLoaders can lead to OOM. Fix problems with concurrent
ignite.compute call.
Key: IGNITE-14131
URL: https://issues.apache.org/jira/browse/IGNITE-14131
Project: Ignite
Issue Type: Improvement
Components: compute
Affects Versions: 2.9.1
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
The root cause of such a problem is growing from assumption that one node can
obtain only one class loader per class name. Thus multiple tasks calling with
different classloaders leads to huge cache grow in server side and finally
leads to oom with jvm metaspace. Additionally we can`t use p2p from multiple
threads, for example ignite instance is shared as a spring bean.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
