[infinispan-issues] [JBoss JIRA] (ISPN-5241) Cache topology updates should use the NO_FC flag

Dan Berindei (JIRA) issues at jboss.org
Tue Feb 24 08:30:50 EST 2015


Dan Berindei created ISPN-5241:
----------------------------------

             Summary: Cache topology updates should use the NO_FC flag
                 Key: ISPN-5241
                 URL: https://issues.jboss.org/browse/ISPN-5241
             Project: Infinispan
          Issue Type: Bug
          Components: Core, State Transfer
    Affects Versions: 7.1.0.Final
            Reporter: Dan Berindei
            Assignee: Dan Berindei
            Priority: Critical
             Fix For: 7.2.0.Final


Topology updates are sent while holding the ClusterCacheStatus lock, so they should never block. However, when MFC is present, the topology update can block waiting for enough credits. As most CacheTopologyControlCommands need to acquire the ClusterCacheStatus lock, this can easily lead to a full remote-executor pool (and OOB pool) and the appearance of a deadlock.

What's more, if one node is not responsive, it can block all the other nodes from receiving further topology updates. Topology updates should be as prompt as possible, so we should use the NO_FC flag to ensure that each node receives topology updates as soon as possible.




--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the infinispan-issues mailing list