Document migration from pids_limit to mem_limit for Docker deployments #8695
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.
Summary
Add documentation note explaining the migration from
pids_limittomem_limitin Docker deployments.Background
A customer experienced PostgreSQL connection failures due to hitting
pids_limit: 100in production. PostgreSQL creates one process per database connection, so this limit restricted deployments to approximately 90-95 concurrent connections before failing.Changes
Added a note to the Docker deployment documentation explaining:
pids_limitwas removed from the deployment configurationmem_limit)Related PR