[
https://issues.apache.org/jira/browse/IGNITE-10244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686578#comment-16686578
]
Yakov Zhdanov commented on IGNITE-10244:
----------------------------------------
[~mcherkas] please rewrite your test to a normal junit then I will take a look.
We already have plenty p2p tests in the project you may use
{{GridAffinityP2PSelfTest}} as example. Tests of the kind use {{extdata}}
modules which are not on tests classpath. This emulates p2p.
If you want to go deeper, please pay attention to
{{org.apache.ignite.internal.managers.deployment.GridDeploymentManager#getGlobalDeployment}}
invocation inside
{{org.apache.ignite.internal.processors.job.GridJobProcessor#processJobExecuteRequest}}
and try to understand why this logic return new deployment or tries to load
inner jobs with different classloaders. You can share debug logs for
{{org.apache.ignite.internal.managers.deployment}} here if you need my comments.
Thanks!
> Peer classloading creates a new class on each call for nested compute tasks
> ---------------------------------------------------------------------------
>
> Key: IGNITE-10244
> URL: https://issues.apache.org/jira/browse/IGNITE-10244
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Mikhail Cherkasov
> Priority: Critical
> Attachments: JustServer.java, MyCall.java, NestedCall.java, Test.java
>
>
> If a compute task has embedded compute tasks, embeded task will be loaded by
> peer class loading as a new class on each call, which leads to metadata OOM.
> Reproducer is attached. Make sure that you run ignite nodes with
> -XX:MaxMetaspaceSize=64m , by default JVM doesn't limit meta space size.
> Also, we need to keep client and server in different JVM to make peer
> classloading be engaged.
> So what happens:
> # client sends compute taks MyCall to server_1
> # server_1 execute MyCall and MyCall sends NestedCall task to server_2
> # server_2 loads NestedCall as a new class and execute it
> # repeat it's again and on second iteration server_2 will load NestedCall as
> new class again, after few iterations this will lead to OOM
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
