Repository navigation
fix(hub): serialize boot migrations with an advisory lock (CL-9605) - #1028
Merged
Merged
Conversation
Concurrent hub boots against one database raced on the one-shot platform SQL's CREATE TYPE (pg_type_typname_nsp_index). Migrations now run under a transaction-scoped Postgres advisory lock.
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.
Concurrent hub boots on one database raced on the platform SQL's CREATE TYPE (pg_type_typname_nsp_index): the present-check and the one-shot migration were not atomic.
migrateHubnow runs under a transaction-scopedpg_advisory_xact_lock, so concurrent boots (e2e suites, rolling deploys) serialize.Verified:
CI=true bun run test:e2egreen 5 times in a row locally.Resolves CL-9605