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

inconsistency issue caused by lock failover during node joining

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 5.1.2.FINAL
    • 5.1.1.FINAL
    • Transactions
    • None

      Scenario:
      tx1 writes to k, hash(k) =

      {A, B}

      . Tx is prepared, commit hasn't been send yet.
      New node C has joined so that ch(k) =

      {C, B}

      , tx1 hasn't completed.
      tx2 writes on k adn prepares/acquire lock on k@C.
      both transactions commit at the same time resulting in B seeing tx2 result and B seeing tx1 result.

              mircea.markus Mircea Markus (Inactive)
              mircea.markus Mircea Markus (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: