Repository navigation
Stage v1.8.7 in production with prepared reads disabled - #1769
Merged
Merged
Conversation
This branch was successfully deployed
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
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.
Deploy the tested prepared-JSON application source as v1.8.7 while explicitly keeping prepared listing reads disabled. Pin registryRolloutCommit to release source 741d575. This allows additive migration 018 and bounded derived-data backfill before a separate activation.
The focused response/update/delete/fallback/rollback tests passed; the saved-record encoding benchmark reduced median time by 63% and allocations by 88%. Broad replay failed with generator port exhaustion and delivery losses; this promotion does not claim peak-capacity acceptance.
Before merge: require successful release/image verification, fresh completed database backup, current-head CI and read-only production preview showing only the intended application update. Keep two apps, 800m CPU, pools60/10, DB/node pools/PVC/network unchanged. Rollback keeps schema018 and protected storage, disabling prepared reads or returning to the old image.