nic-6443 commented on issue #10429:
URL: https://github.com/apache/apisix/issues/10429#issuecomment-4676892526
I believe this was fixed on the runtime side rather than in the Lua code.
The dubbo-proxy path multiplexes requests onto a shared upstream connection via
a per-request "fake" upstream, and that fake upstream didn't inherit the
per-request connect/send/read timeouts APISIX sets, so they defaulted to 0 —
requests attached to a main connection that was still connecting (your `multi:
connect reuse unfinished` lines) timed out instantly, which matches the 504s
with ~0.000s upstream time right at the start of the benchmark.
This was fixed by api7/ngx_multi_upstream_module#16 ("fix: missing fake
upstream timeout"), shipped in module 1.3.2 and bundled into apisix-runtime
starting with APISIX 3.13.0. Could you retest on 3.13.0+ (ideally current
3.16)? If the startup 504s are gone I'd suggest closing this; if they're still
there, fresh logs would help.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
