You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (JIRA)" <ji...@apache.org> on 2015/12/11 17:20:10 UTC
[jira] [Resolved] (IGNITE-2106) BinaryMarshaller: near cache
mustn't keep a copy on put() operation
[ https://issues.apache.org/jira/browse/IGNITE-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anton Vinogradov resolved IGNITE-2106.
--------------------------------------
Resolution: Fixed
Problem was with incorrect near entry invalidation when node becomes backup for this entry.
Fixed. New test added.
> BinaryMarshaller: near cache mustn't keep a copy on put() operation
> -------------------------------------------------------------------
>
> Key: IGNITE-2106
> URL: https://issues.apache.org/jira/browse/IGNITE-2106
> Project: Ignite
> Issue Type: Bug
> Reporter: Anton Vinogradov
> Assignee: Anton Vinogradov
> Priority: Blocker
>
> Binary marshaller is an opensouced Gridgain Prortable marshaller,
> So bug http://atlassian.gridgain.com/jira/browse/GG-10791 moved to Ignite jira.
> There are several deployment related tests that fail when PortableMarshaller is used.
> GridPortableCacheDeploymentSelftTest.testDeployment3()/testDeployemnt4();
> GridPortableCacheDeploymentOffHeapSelfTest.testDeployment3()/testDeployemnt4();
> The reason of the failure is that a near cache stores a copy of a cache entry when the cache.put() is being executed. No cache.get() was explicitly called during the test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)