[
https://issues.apache.org/jira/browse/FLINK-40788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18141091#comment-18141091
]
Martijn Visser commented on FLINK-40788:
----------------------------------------
Correction on my earlier comment: metaspace did grow. The TaskManagers peak at
about 52 MiB on 1.20 and 2.2 and 57 MiB on 2.3 and later, because since
FLINK-38912 the RPC class loader loads a second copy of the shaded Netty
classes. FLINK-41389 fixes that and the test passes at 64m again, so I'll close
my PR that raised the limit.
> 'Heavy deployment end-to-end test' fails because all TaskManagers run out of
> memory on Java 11
> ----------------------------------------------------------------------------------------------
>
> Key: FLINK-40788
> URL: https://issues.apache.org/jira/browse/FLINK-40788
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Affects Versions: 2.4.0
> Reporter: Martijn Visser
> Assignee: Martijn Visser
> Priority: Major
> Labels: pull-request-available, test-stability
>
> The heavy deployment end-to-end test failed in the Java 11 nightly on master:
> https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=79325&view=logs&j=320b3f94-fe78-5d7f-e965-9db30de9270e
> {code}
> Caused by: org.apache.flink.runtime.JobException: Recovery is suppressed by
> FixedDelayRestartBackoffTimeStrategy(maxNumberRestartAttempts=3,
> backoffTimeMS=0)
> ...
> Caused by:
> org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException:
> Could not acquire the minimum required resources.
> [FAIL] 'Heavy deployment end-to-end test' failed after 5 minutes and 12
> seconds! Test exited with exit code 1
> {code}
> All five TaskManagers logged an OutOfMemoryError during deployment, three
> "Java heap space" and two "Metaspace", before the job gave up. FLINK-16456
> had the same symptom on Java 11 in 2020.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
