You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "James Bench (JIRA)" <ji...@apache.org> on 2015/09/25 16:53:04 UTC
[jira] [Updated] (IGNITE-1551) IgniteCache.put hangs indefinatly
[ https://issues.apache.org/jira/browse/IGNITE-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Bench updated IGNITE-1551:
--------------------------------
Description:
We have a process that pulls jobs from a queue and puts associated assets into a cache using IgniteCache.put.
The object we put into the cache is an object holding a map of Enums and byte arrays.
{code}
private Map<AssetTypeEnum, byte[]> assets = new EnumMap<>(AssetTypeEnum.class);
{code}
We are using a UUID as the key.
The byte arrays can become quite large - the batch it was processing when the issue occurred were up to 30mb in size.
The thread got stuck in {code}IgniteCache.put{code} and remained stuck for a few hours until we restarted Tomcat.
I took a memory Snapshot using YourKit while the application was frozen (https://onedrive.live.com/redir?resid=F06891F3AE093614!892&authkey=!AMfOdu7-jEtk_KA&ithint=file%2csnapshot) which shows the thread {{taskExecutorBean-3}} waiting in sun.misc.Unsafe.park. It has spent 100% of the time I profiled here.
was:
We have a process that pulls jobs from a queue and puts associated assets into a cache using IgniteCache.put.
The object we put into the cache is an object holding a map of Enums and byte arrays.
{code}
private Map<AssetTypeEnum, byte[]> assets = new EnumMap<>(AssetTypeEnum.class);
{code}
We are using a UUID as the key.
The byte arrays can become quite large - the batch it was processing when the issue occurred were up to 30mb in size.
The thread got stuck in {code}IgniteCache.put{code} and remained stuck for a few hours until we restarted Tomcat.
I took a memory Snapshot using YourKit while the application was frozen (attached) which shows the thread {{taskExecutorBean-3}} waiting in sun.misc.Unsafe.park. It has spent 100% of the time I profiled here.
> IgniteCache.put hangs indefinatly
> ---------------------------------
>
> Key: IGNITE-1551
> URL: https://issues.apache.org/jira/browse/IGNITE-1551
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Environment: Ubuntu 14.04
> java version "1.8.0_51"
> Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
> Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
> Tomcat 7
> Reporter: James Bench
>
> We have a process that pulls jobs from a queue and puts associated assets into a cache using IgniteCache.put.
> The object we put into the cache is an object holding a map of Enums and byte arrays.
> {code}
> private Map<AssetTypeEnum, byte[]> assets = new EnumMap<>(AssetTypeEnum.class);
> {code}
> We are using a UUID as the key.
> The byte arrays can become quite large - the batch it was processing when the issue occurred were up to 30mb in size.
> The thread got stuck in {code}IgniteCache.put{code} and remained stuck for a few hours until we restarted Tomcat.
> I took a memory Snapshot using YourKit while the application was frozen (https://onedrive.live.com/redir?resid=F06891F3AE093614!892&authkey=!AMfOdu7-jEtk_KA&ithint=file%2csnapshot) which shows the thread {{taskExecutorBean-3}} waiting in sun.misc.Unsafe.park. It has spent 100% of the time I profiled here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)