Aias00 opened a new issue, #7644: URL: https://github.com/apache/shenyu/issues/7644
## Goal Make outbound connection and acquisition capacity explicit and measurable under load. This is separate from the keep-alive default change tracked by #6574. ## Current evidence `HttpClientFactory.buildElasticConnectionPool` sets `maxConnections(Integer.MAX_VALUE)` and `pendingAcquireMaxCount(-1)`. FIXED pool wiring configures max connections and acquisition timeout, but does not expose an explicit acquisition-queue count in this factory. These are source observations, not a measured production incident. FIXED is the current properties default; do not describe ELASTIC as the default. [Source at reviewed commit](https://github.com/apache/shenyu/blob/b4e115367fd57adc8aba332d655b1009932ba394/shenyu-spring-boot-starter/shenyu-spring-boot-starter-plugin/shenyu-spring-boot-starter-plugin-httpclient/src/main/java/org/apache/shenyu/springboot/starter/plugin/httpclient/HttpClientFactory.java#L180) ## Scope and acceptance criteria - [ ] Benchmark current FIXED behavior and keep-alive reuse using a controlled upstream, including slow responses and overload. - [ ] Define/configure finite acquisition queue capacity and timeout where required; retain backward compatibility or clearly document any default change. - [ ] Expose or reuse active/idle/pending/acquire-timeout metrics with bounded labels. - [ ] Document pool sizing in terms of measured upstream capacity and occupancy; evaluate HTTP and AI streaming pools separately before choosing isolation. - [ ] Compare successful throughput, p99, new connections/sec, pending duration, FD count and memory. - [ ] Overload has bounded resources and predictable failure/recovery; cancellation and timeout release capacity. - [ ] Keep #6574 as the owner of the keep-alive default fix; do not duplicate that change here. -- 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]
