Cached HBase connection eviction vs. Phoenix Query Server centralization: trading pool controllability for latency under intermittent exhaustion
Intermittent connection pool exhaustion in Phoenix often stems from ambiguous root causes when cached HBase connections are shared across the JDBC client pool. The documented thick driver caches a single HBase Connection per client configuration, and closing the JDBC connection does not guarantee release of region-server resources; eviction is governed by HB
