[infinispan-issues] [JBoss JIRA] (ISPN-9852) Invocations waiting for a new topology should resume in parallel

Dan Berindei (Jira) issues at jboss.org
Sun Jan 6 13:06:00 EST 2019


Dan Berindei created ISPN-9852:
----------------------------------

             Summary: Invocations waiting for a new topology should resume in parallel
                 Key: ISPN-9852
                 URL: https://issues.jboss.org/browse/ISPN-9852
             Project: Infinispan
          Issue Type: Bug
          Components: Core
    Affects Versions: 9.4.5.Final, 10.0.0.Alpha2
            Reporter: Dan Berindei
             Fix For: 10.0.0.Beta2


When a command requires a topology newer than the current topology, it uses {{StateTransferLock.transactionDataFuture()}} to wait for the newer topology. When the tx data is received for the newer topology, some (most?) of the waiting operations  do not use a separate executor, instead they are all resumed on the thread that received the tx data. If some operations block (e.g. because of a store), it could take a very long time to finish all the blocked operations.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the infinispan-issues mailing list