Spring gateway use reactor netty switch thread spend too many time about reactor-netty HOT 7 CLOSED

@will-zdu I'm closing this one. Please upgrade to a supported version and if the problem still exists, provide some reproducible example.

from reactor-netty.

@will-zdu You are using an unsupported version, also there is a known regression in 0.9.10 that is fixed in 0.9.14. I would strongly encourage you to update your versions.

https://github.com/reactor/reactor-netty/releases/tag/v0.9.14.RELEASE

from reactor-netty.

@violetagg #1371
I have seen your modification, but I still don't understand the root cause of this problem. How does subsrcibe not executing in eventloop cause race condition with request, which leads to long execution time,Could you please help me explain, or provide key relevant information, or I need to read that part of the relevant document
In my understanding, this may be the cause of the problem,
reactor.netty.channel.FluxReceive#drainReceiver
In this method,
If "receiver" is empty, then keep checking the loop until "receiver" is not empty and it works, but I still haven't found the reason why most of them are about 6 seconds out. Does it have something to do with that configuration?
If the request call is executed before subscribe, and subscribe is not in eventloop, is it because receiver is empty, but the eventloop thread keeps looping, and receiver is not volatile, resulting in eventloop The reason for cache consistency in the thread cannot be found even if the receiver is no longer empty

from reactor-netty.

@will-zdu Did you update at least to the latest available 0.9.x release?

from reactor-netty.

@violetagg have changed to use 0.9.14.release,but stil found timeout,but when restart it and check it again,no timeout found

from reactor-netty.

@will-zdu If 0.9.14 doesn't solve the issue ... I can only recommend to upgrade to a supported version and if the problem still exists, to provide some reproducible example.

from reactor-netty.

@violetagg 0.9.14 reproduce again in product env,now we try to use the latest available 0.9.x release

from reactor-netty.