Make everything use the private IP for pg_bouncer except for the deployer for migrations. #2164
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Functional tests
I've deployed a dev stack with this!
Checklist