The current behaviour is suspicious. The call to ap_proxy_initialize_worker has basically no effect and without this change the connection to backend fails from time to time (when running perf tests with dynamic worker removal) which causes all workers in error state (= 503) even though a corresponding node to the worker is up and running.
The current behaviour is suspicious. The call to
ap_proxy_initialize_worker
has basically no effect and without this change the connection to backend fails from time to time (when running perf tests with dynamic worker removal) which causesall workers in error state
(= 503) even though a corresponding node to the worker is up and running.