Repository navigation
deploy: update prod to v1.7.4 - #1226
Merged
Merged
Conversation
Promotes #1225: registry pod memory request 256Mi→512Mi, limit 512Mi→1Gi. Sized for the doubled pgxpool MaxConns (60/pod after #1221) — pgxpool keeps per-connection state in the Go process so memory grew from ~330MB peak to ~450MB peak under scraper load. Pod tx49f was OOMKilled at 17:01 UTC on 2026-04-29 against the old 512MiB ceiling. Zero downtime deploy — Deployment template change only, no PG involvement. Staging picked up the new limits cleanly via deploy-staging on the merge of #1225, both pods stayed healthy through the rolling update. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Promotes v1.7.4 (#1225) to production: registry pod memory request
256Mi → 512Mi, limit512Mi → 1Gi.Why
#1221 doubled pgxpool
MaxConns30→60 per pod without bumping the registry pod memory limit. pgxpool keeps per-connection state in the Go process (prepared statement cache, scratch buffers, row iteration state) so peak per-pod memory shifted from ~330 MB to ~450 MB against the 512 MiB limit. Podtx49fwas OOMKilled at 17:01 UTC on 2026-04-29.Validation so far
deploy-staging.ymlafter fix(deploy): bump registry pod memory to match doubled pgxpool size #1225 mergedreq=512Mi limit=1Gi✓Deployment
Zero downtime — Deployment template change only, rolling update with
maxSurge: 1, maxUnavailable: 0. No PG involvement (nomax_connectionschange, no shared_preload_libraries change).Test plan
ghcr.io/modelcontextprotocol/registry:1.7.4)req=512Mi limit=1Gi🤖 Generated with Claude Code