[
https://issues.apache.org/jira/browse/IGNITE-14131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282929#comment-17282929
]
Ignite TC Bot commented on IGNITE-14131:
----------------------------------------
{panel:title=Branch: [pull/8759/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}JCache TCK 1.1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5868691]]
{panel}
{panel:title=Branch: [pull/8759/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5867667&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Priority: Major
> Time Spent: 1h 10m
> 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)
