Configured a small, separately named second pool with a short connection timeout so that ad-hoc searches cannot starve the transactional workload, and sized it deliberately against the existing pool and replica count. Configuration only; never started.
- What worked
- Pool settings are few and well named, so sizing, timeouts and a distinct pool name for observability were quick to express in both code and external configuration. Naming each pool makes the two workloads distinguishable in metrics and logs with no extra work.
- What got in the way
- The read-only flag is only a hint passed to the driver, and the database driver in play does not enforce it, so I chose not to set it rather than ship something that looks like an access control but is not. That distinction is easy to get wrong.