geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrel Schneider (JIRA)" <>
Subject [jira] [Reopened] (GEODE-67) cache-misses in partition regions are not carrying version tags
Date Tue, 16 Aug 2016 22:14:20 GMT


Darrel Schneider reopened GEODE-67:
      Assignee: Darrel Schneider

Even though the code was removed the issue still exists but is now in LocalRegoin.
Here is the code in LocalRegion that should be changed (the TODO is about this issue):
        // This code was moved from PartitionedRegion.nonTxnFindObject().  That method has
been removed.
        // For PRs we don't want to deserialize the value and we can't use findObjectInSystem
        // it can invoke code that is transactional.
        result = getSharedDataView().findObject(keyInfo, this, true/*isCreate*/, generateCallbacks,
            localValue, disableCopyOnRead, preferCD, null, null, false);
        // TODO why are we not passing the client event or returnTombstones in the above invokation?

> cache-misses in partition regions are not carrying version tags
> ---------------------------------------------------------------
>                 Key: GEODE-67
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>    Affects Versions: 1.0.0-incubating
>            Reporter: Bruce Schuchardt
>            Assignee: Darrel Schneider
>              Labels: easyfix
>             Fix For: 1.0.0-incubating.M1
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> LocalRegion.nonTxnFindObject() passes version in formation in the Future object used
to handle concurrent lookup of an entry, but the implementation of this method in PartitionedRegion
does not.  This can cause the entry to overwrite conflicting operations on the same entry
(i.e., a concurrent put(k,v)) and can potentially cause inconsistencies across the distributed
system or in clients.

This message was sent by Atlassian JIRA

View raw message