Page MenuHomeSoftware Heritage

Migrate services to use pgbouncer instances
ClosedPublic

Authored by ardumont on Thu, Jun 6, 6:35 PM.

Details

Summary
  • Migrate existing services (storage, listers, etc...) to use bouncer (instead of direct db accesses)
  • somerset: Reference the indexer db in somerset's pgbouncer instance
  • Migrate indexer-storage service to use somerset's pgbouncer instance

Related T1784

Test Plan

bin/octocatalog-diff

Diff Detail

Repository
rSPSITE puppet-swh-site
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

ardumont created this revision.Thu, Jun 6, 6:35 PM
ardumont planned changes to this revision.Fri, Jun 7, 10:50 AM
ardumont added a comment.EditedFri, Jun 7, 10:56 AM

I want to make sure of something first in regards to the pgbouncer instances.

I want to make sure of something first in regards to the pgbouncer instances.

Yes, there was a hit and miss adaptations for belvedere, fixed now.

ardumont updated this revision to Diff 5125.Fri, Jun 7, 11:05 AM

Use the right ports (secondary cluster) for the belvedere connections

vlorentz accepted this revision.Fri, Jun 7, 11:33 AM
This revision is now accepted and ready to land.Fri, Jun 7, 11:33 AM
ardumont updated this revision to Diff 5126.Fri, Jun 7, 11:37 AM

Plug diff to branch production

This revision was automatically updated to reflect the committed changes.