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

Two concurrent putIfAbsent operations can both return null during rebalance

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Critical
    • None
    • 6.0.2.Final
    • Core, State Transfer

    Description

      If the cache topology changes while executing a putIfAbsent operation, the old primary owner will throw an OutdatedTopologyException, and the originator will retry on the new owner.

      When retrying the PutKeyValueCommand on the new primary owner, we compare the current value with the command's new value. If they are equal, we assume that the initial command wrote the old value, and we return null.

      However, the value might have been written by another putIfAbsent operation. So we could have two putIfAbsent(k, v) operations, both returning null.

      A is the originator, B is the primary owner, k = null
A -> B: putIfAbsent(k, v1)
B dies before writing v, C is now primary owner
D -> C: putIfAbsent(k, v1) // another put operation from D, with the same value
C -> D: null // correct
A -> C: retry_putIfAbsent(k, v1)
C -> A: null // C assumes A is overwriting its own value, so it's also returning null

      Attachments

        Issue Links

          is incorporated by

          Task - A task that needs to be done. ISPN-7590 Invocation idempotence

          • 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.
          • Open
          is related to

          Bug - A problem which impairs or prevents the functions of the product. ISPN-3918 Inconsistent view of the cache with putIfAbsent in a non-tx cache during state transfer

          • 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.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. ISPN-3422 In non-tx caches, write operations may not be atomic during rebalance

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

          Bug - A problem which impairs or prevents the functions of the product. ISPN-2956 putIfAbsent on Hot Rod Java client doesn't reliably fulfil contract

          • 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

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: ISPN

              People

                Unassigned Unassigned
                dberinde@redhat.com Dan Berindei
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated: