]
Dan Berindei resolved ISPN-9852.
--------------------------------
Fix Version/s: (was: 9.4.16.Final)
Resolution: Out of Date
With ISPN-10309 we are moving the blocking operations to a separate thread pool, so this
is no longer relevant.
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
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.