[
https://issues.apache.org/jira/browse/IGNITE-24670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-24670:
---------------------------------------
Description:
RestComponent uses Micronaut under the hood. The latter registers a shutdown
hook; Micronaut is designed to be 'the framework' that only stops with the
application, so it has no means to remove its shutdown hook. The hook causes
2.15Mb of heap to leak. If we run a lot of integration tests (which start and
stop Ignite instances), the leaked heap sums up (2.15 Mb per Ignite instance).
This is especially visible when repeatedly running a test (until failure) that
spins up (and then stops) a few Ignite instances. Just about 50 runs eat up
about 1Gb of the heap.
We could forcibly remove Micronaut hooks using reflection after each test.
> Micronaut shutdown hooks leak in integration tests
> --------------------------------------------------
>
> Key: IGNITE-24670
> URL: https://issues.apache.org/jira/browse/IGNITE-24670
> Project: Ignite
> Issue Type: Bug
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> RestComponent uses Micronaut under the hood. The latter registers a shutdown
> hook; Micronaut is designed to be 'the framework' that only stops with the
> application, so it has no means to remove its shutdown hook. The hook causes
> 2.15Mb of heap to leak. If we run a lot of integration tests (which start and
> stop Ignite instances), the leaked heap sums up (2.15 Mb per Ignite instance).
> This is especially visible when repeatedly running a test (until failure)
> that spins up (and then stops) a few Ignite instances. Just about 50 runs eat
> up about 1Gb of the heap.
> We could forcibly remove Micronaut hooks using reflection after each test.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
