The method org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(Collection<Address>, ReplicableCommand, RpcOptions) is implemented by blocking on a CompletableFuture, but this then stalls on java.util.concurrent.CompletableFuture.waitingGet(boolean) by spending a significant amount of CPU time by spinning.

When implementing RPC calls and having to wait for remote operations, spinning is probably not a good idea. Could we try implementing this in some way to hint towards a more pessimistic lock?