Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make everything use the private IP for pg_bouncer except for the deployer for migrations. #2164

Merged
merged 3 commits into from
Feb 26, 2020

Conversation

kurtwheeler
Copy link
Contributor

Issue Number

N/A Came up while trying to process data

Purpose/Implementation Notes

The worker instances can't connect to the pg_bouncer instance, but the foreman and the API can. As far as I can tell the only difference between them is that the worker instances are using the public instead of private IP. I have no idea why this makes a difference. However apparently it does so this should fix it!

This fixes the issue by making the worker instances use the private IP for the pg_bouncer instance and the only thing that doesn't now is the deployer itself.

I also bumped max_clients to 1 for the staging stack so we can test actually processing in staging!

Types of changes

  • Bugfix (non-breaking change which fixes an issue)

Functional tests

I've deployed a dev stack with this!

Checklist

  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants