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

[Tristan Tarrant (Jira)]

     [ https://issues.jboss.org/browse/ISPN-9852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tristan Tarrant updated ISPN-9852:
----------------------------------
    Fix Version/s: 9.4.15.Final
                       (was: 9.4.14.Final)


> 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: 8.2.11.Final, 10.0.0.Alpha2, 9.4.5.Final
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>            Priority: Major
>             Fix For: 10.0.0.Beta4, 9.4.15.Final
>
>
> 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)