Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-2903

Manual eviction should not delete entry from cache store

    XMLWordPrintable

Details

    Description

      Here's the scenario:

      Given 2 nodes with REPL_SYNC cache with passivating cache store (e.g. default web cache in AS7).

      1. Create cache entry containing atomic map with 2 map entries on node1.
      2. Passivate that cache entry on node2 via manual evict.
      3. Modify 1 of the atomic map entries within the cache entry on node1.
      4. Lookup atomic map on node2. It only contains 1 map entry - the map entry modified in step 3. The other map entry is lost.

      It's a side effect of ISPN-2384, where some changes were made to tighten the passivation/activation scenarios, but it did not cover manual eviction calls.

      Attachments

        1. AtomicMapServlet.java
          4 kB
        2. AtomicMapTestCase.java
          5 kB
        3. server.log
          1.12 MB
        4. server.log
          1.12 MB

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. AS7-4932 CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          clones

          Bug - A problem that impairs or prevents the functions of the product. ISPN-2095 Eviction causes lost AtomicMap entries

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-2384 Entry lost after Eviction/Passivation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ISPN-3613 Stored entries are deleted from table in rebalance

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. MODE-1733 Problems with defining node types in clustered environment with eviction enabled

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              rh-ee-galder Galder Zamarreño
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: