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

Default optimistic locking configuration leads to inconsistency

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Blocker
    • None
    • 5.3.0.Final, 6.0.0.CR1
    • Configuration, Transactions

    Description

      Infinispan transactional caches are configured with optimistic locking by default. Without extra configuration (REPETEABLE_READ + writeSkews), concurrent replace() calls will return true under contention and transactions will commit.

      Under contention, even if replace() returns true for multiple resources, it should rollback all except one transaction.

      When transactional optimistic locking is enabled (default), it should enable all options required to make this scenarios correct.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. ISPN-3677 With optimistic TX, conditional commands may wrongly succeed

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

          Sub-task - The sub-task of the issue ISPN-7613 Enable write-skew for optimistic + repeatable-read transactions

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-3927 rethinking ISPN transactions

          • 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.
          • To Do

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-5691 Server should enable writeSkew for some configurations by default

          • 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

              rh-ee-galder Galder Zamarreño
              rh-ee-galder Galder Zamarreño
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: