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

Remove-inconsistency during NBST

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 5.2.0.Beta6
    • 5.2.0.Alpha3
    • State Transfer
    • None

    Description

      The NBST functionality leaves place to inconsistencies during removals:
      1. the joiner first requests transaction data
      2. after all transaction data is integrated (i.e. tx is prepared on the state receiver node) it requests the rest(data container) of the data
      3. in order not to override the data from transactions which is more recent (transactions at step 1 might commit during step 2), the insertion at 2 happens with putIfAbsent. Whilst this prevents from overriding newer values (written by transactions), it doesn't guard against the situation in which the tx at step 1 removed data. So it is possible for deleted data a to resurrect.

      A solution to this inconsistency issue is to use tombstones for the duration of the state transfer.

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. ISPN-2502 State transfer can lead to inconsitencies because it applies data using putIfAbsent without locking

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-2658 org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments

          • 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

            People

              anistor Adrian Nistor (Inactive)
              mircea.markus Mircea Markus (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: