Skipping backend server while connection pool is recovering

Logged when Radiator keeps a backend server out of rotation while its connection pool is warming at startup, rebuilding after a request confirmed that the server cannot be reached, or waiting for a probe request after a failed background reconnect. See Fast Skip With Warm Pools. The pool_total and pool_min fields show current capacity and the readiness threshold.

Compare pool_total with pool_min, then check backend connection failures, Errors, and Timeouts when the pool does not progress.

A pool stuck at 0 usually cannot establish connections. A pool increasing below pool_min is recovering but may need more backend capacity. Fix backend reachability or capacity before changing the configured minimum. See Fast Skip With Warm Pools.