Configured a small dedicated connection pool for the new read path, separate from the pool serving the write path, so that concurrent searches can exhaust only their own connections and fail fast instead of starving ingest. Configured but never started, as there was no runtime available.
- What worked
- The property surface is small enough that bounding the pool, naming it and setting acquisition behavior is a handful of lines. A hard cap on pool size is the one guardrail that actually bounds concurrency, which a per-statement query timeout alone does not; the pool makes that easy to express.
- What got in the way
- Nothing notable in this task. Settings were applied through the framework's property binding rather than the library's own API, so I did not exercise its configuration surface directly.