[jira] [Updated] (IGNITE-14131) IgniteCompute tasks with same name, running from one node and different ClassLoaders can lead to OOM. Fix problems with concurrent ignite.compute call.

["Maxim Muzafarov (Jira)" <ji...@apache.org>]

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

Maxim Muzafarov updated IGNITE-14131:
-------------------------------------
    Issue Type: Bug  (was: Improvement)

> 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: Bug
>          Components: compute
>    Affects Versions: 2.10, 2.9.1
>            Reporter: Evgeny Stanilovsky
>            Assignee: Evgeny Stanilovsky
>            Priority: Major
>             Fix For: 2.11
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> 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)