[infinispan-issues] [JBoss JIRA] (ISPN-4610) Implement total order for non-transactional caches

[Dan Berindei (JIRA)]

Dan Berindei created ISPN-4610:
----------------------------------

             Summary: Implement total order for non-transactional caches
                 Key: ISPN-4610
                 URL: https://issues.jboss.org/browse/ISPN-4610
             Project: Infinispan
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Core
    Affects Versions: 7.0.0.Alpha5
            Reporter: Dan Berindei
            Assignee: Pedro Ruivo
             Fix For: 7.0.0.Final


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.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)