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

rehashing inconsistency when eagerLockSingleNode enabled

    XMLWordPrintable

    Details

      Description

      When eagerLockSingleNode="true", if the main data owner of a key changes during a transaction then the k might end up in inconsistent state.
      A solution to avoid this is:

      • on topology change, if a eagerLockSingleNode is enabled, iterate over all transactions's keys
      • if the main owner for a key has changed then just mark the tx for rollback

      This way, on next operation for that transaction an exception should be thrown, e.g. TxRollbackOnlyException

        Attachments

          Activity

            People

            Assignee:
            mircea.markus Mircea Markus (Inactive)
            Reporter:
            mircea.markus Mircea Markus (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: