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

Implement total order for non-transactional caches

    XMLWordPrintable

Details

    • Feature Request
    • Status: Open (View Workflow)
    • Optional
    • Resolution: Unresolved
    • 7.0.0.Alpha5
    • None
    • Core
    • None

    Description

      Current locking algorithm in non-transactional caches needs a remote thread on the primary owner to block while replicating the update to the backup owner. The thread is also holding the lock for the key, so it's blocking other threads that want to write to the same key. When there is a lot of contention, this can exhaust the remote executor thread pool and cause lock timeouts.

      TO was designed with high contention in mind, and it doesn't block threads to acquire locks. So it should handle this much better.

      An alternative solution would be the locking rework in ISPN-2849.

      Attachments

        Issue Links

          Activity

            People

              pruivo@redhat.com Pedro Ruivo
              dberinde@redhat.com Dan Berindei
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: