You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/08 13:12:00 UTC
[jira] [Updated] (IGNITE-10858) Memory can not be timely recovery
when executing the ignite service with thread pool
[ https://issues.apache.org/jira/browse/IGNITE-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-10858:
-------------------------------------
Fix Version/s: (was: 2.8)
2.9
> Memory can not be timely recovery when executing the ignite service with thread pool
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-10858
> URL: https://issues.apache.org/jira/browse/IGNITE-10858
> Project: Ignite
> Issue Type: Bug
> Components: binary
> Affects Versions: 2.7
> Reporter: renx
> Priority: Major
> Fix For: 2.9
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> I integrate IgniteClient into J2EE. In the HTTP-Request thread calls Ignite Service which the parameter's serialization is larger (about 100MB). By observing JVM console, I find that the memory occupancy is very bad. Through JVM dump, I find that ThreadLocal causes OptimizedObjectStreamRegistry.StreamHolder memory leak, which can be solved by the following modifications.
> org.apache.ignite.internal.util.io.GridUnsafeDataOutput#reset:
> {code:java}
> public void reset(){
> off = 0;
> out = null;
> // clear data
> this.bytes = new byte[0];
> this.maxOff = 0;
> this.lastCheck = U.currentTimeMillis();
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)