We currently set the connection pool host timeout to 5min here. On the scale of some patterns of work (notably, mirrored reads), this may cause us to unnecessarily drop and recreate pools, which can be an expensive operation when the minimum pool size is set. Pool expiry also emits a mildly concerning message when seen in logs. We should set this host timeout to a larger value ala an hour.

Acceptance Criteria: 

Determine if the existing configurability is sufficient or if we need to change the default timeout (and change if needed). If new grad picks up this ticket, reach out in a team channel for a current answer.