[jira] [Updated] (IGNITE-3372) IgniteDataStreamer: pre-loading starvation if multiple streamers preload the same cache

["Denis Magda (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Magda updated IGNITE-3372:
--------------------------------
    Attachment: jstack2.log

> IgniteDataStreamer: pre-loading starvation if multiple streamers preload the same cache
> ---------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3372
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3372
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Magda
>            Assignee: Denis Magda
>            Priority: Critical
>         Attachments: jstack2.log
>
>
> If to start preloading a cache from multiple streamers on a node that owns partitions that are being preloaded then we will get performance degradation at some point in cases if:
> - BinaryMarshaller is used;
> - an entry key is a custom object for which we store data in metadata cache.
> The main reason according to the thread dumps attached is a race-condition around 
> {{org.apache.ignite.internal.processors.cache.GridCacheMapEntry.obsolete(GridCacheMapEntry.java:2888)}}
> To improve the performance both {{GridDhtPartitionTopologyImpl.onRemove}} and {{GridDhtPartitionTopologyImpl.onAdded}} must reuse a partition number that is hold in entry.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)