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

Read-after-write semantics in transactional mode

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Rejected
    • 6.0.0.Alpha3
    • None
    • Transactions
    • None

    Description

      In dist sync tx (optimistic, read committed) mode I'd expect that in this situation:

      A=1, B=1

      startTx
      write A=2
      write B=2
      endTx

      if on different node I read B=2, it implies that A=2.
      However, as entries are committed during the commit phase in non-defined order (according to context map iteration order), it may happen that B is committed to 2, B is read as 2, A is read as 1 and only after that A is committed to 2.

      That is pretty unexpected semantics. It even means that the transactions are not atomic with regards to read operations.

      Attachments

        Activity

          People

            mircea.markus Mircea Markus (Inactive)
            rvansa1@redhat.com Radim Vansa
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: