[jira] [Resolved] (IGNITE-2620) Extra 'entry expired' events

["Semen Boikov (JIRA)" <ji...@apache.org>]

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

Semen Boikov resolved IGNITE-2620.
----------------------------------
    Resolution: Fixed
      Assignee:     (was: Semen Boikov)

Fixed several issues:
- need retry GridCacheMapEntry.onTtlExpired if entry is obsolete 
- should not clear expired entry if mvcc is not empty
- do not call QueryManager.onSwap when swap entry based on offheap pointer

Merger into master (commit 46892c7).

> Extra 'entry expired' events
> ----------------------------
>
>                 Key: IGNITE-2620
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2620
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.5.0.final
>            Reporter: Semen Boikov
>
> Added test reproducing issue: IgniteCacheEntryListenerExpiredEventsTest (more then 1 event can be fired for single entry expiration).
> Very suspicious place is GridCacheMapEntry.onTtlExpired: even when entry is obsolete it calls 'clearIndex' and 'releaseSwap' (these calls should be prohibited for obsolete entry).



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