[FOLIO-3761] Update DB_MAXPOOLSIZE for mod-agreements in reference environments Created: 19/Apr/23  Updated: 20/Apr/23  Resolved: 19/Apr/23

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Sprint 160
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

mod-agreements needs a large connection pool for additional tenants. Owen Stephens reports:

Snapshot seems to have multiple tenants running on it and we think this is causing some issues for mod-agreements possibly due to the number of database connections available (DB_MAXPOOLSIZE="10").
[...] could we get the db_maxpoolsize doubled for mod-agreements?



 Comments   
Comment by Wayne Schneider [ 19/Apr/23 ]

This change has been made to the variables files for the snapshot, Nolana, and Orchid reference builds.

Generated at Thu Feb 08 23:30:30 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.