-
Notifications
You must be signed in to change notification settings - Fork 59
Fix CREATE TYPE race that can crash the worker on first boot #436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
vedarolap
wants to merge
3
commits into
roostorg:main
Choose a base branch
from
vedarolap:fix/postgres-schema-create-race
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+81
−2
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
57 changes: 57 additions & 0 deletions
57
osprey_worker/src/osprey/worker/lib/storage/tests/test_postgres.py
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,57 @@ | ||
| import threading | ||
|
|
||
| import sqlalchemy | ||
| from osprey.worker.lib.singletons import CONFIG | ||
| from osprey.worker.lib.storage import postgres | ||
| from psycopg2.errors import DuplicateDatabase, InvalidCatalogName | ||
| from sqlalchemy.exc import ProgrammingError | ||
| from sqlalchemy_utils import create_database, drop_database | ||
|
|
||
|
|
||
| def test_create_schema_survives_concurrent_callers_on_a_fresh_database(): | ||
| """Regression test for issue #432: on a fresh database, two processes (e.g. the worker and | ||
| the UI API) both calling create_schema() at startup used to be able to race on `CREATE TYPE` | ||
| for the job_status enum, since SQLAlchemy's enum creation is check-then-create rather than | ||
| atomic. Both would see the type as missing, both would issue CREATE TYPE, and the loser would | ||
| crash with a UniqueViolation on `pg_type_typname_nsp_index`. | ||
|
|
||
| Simulate two racing processes with two independent engines hitting a brand new database at | ||
| the same time, and assert neither raises. | ||
| """ | ||
| base_url = CONFIG.instance()['POSTGRES_HOSTS']['osprey_db'] | ||
| fresh_url = base_url.rsplit('/', 1)[0] + '/osprey_test_concurrent_schema_create' | ||
|
|
||
| try: | ||
| drop_database(fresh_url) | ||
| except ProgrammingError as e: | ||
| if not isinstance(e.orig, InvalidCatalogName): | ||
| raise | ||
| try: | ||
| create_database(fresh_url) | ||
| except ProgrammingError as e: | ||
| if not isinstance(e.orig, DuplicateDatabase): | ||
| raise | ||
|
|
||
| try: | ||
| errors: list[Exception] = [] | ||
| barrier = threading.Barrier(2) | ||
|
|
||
| def _create_schema() -> None: | ||
| engine = sqlalchemy.create_engine(fresh_url) | ||
| try: | ||
| barrier.wait(timeout=5) | ||
| postgres.create_schema(engine) | ||
| except Exception as e: | ||
| errors.append(e) | ||
| finally: | ||
| engine.dispose() | ||
|
|
||
| threads = [threading.Thread(target=_create_schema) for _ in range(2)] | ||
| for thread in threads: | ||
| thread.start() | ||
| for thread in threads: | ||
| thread.join(timeout=10) | ||
|
|
||
| assert not errors, errors | ||
| finally: | ||
| drop_database(fresh_url) | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Fail the test explicitly if a thread times out.
In Python,
thread.join(timeout=10)returns silently without raising an exception when the timeout expires. If this concurrency test were to deadlock, the threads would hang,joinwould return silently, anderrorswould remain empty. The test would pass theassert not errorscheck and then fail confusingly during thedrop_databaseteardown (because the hung threads hold active connections).Checking
thread.is_alive()after joining ensures that deadlocks are reported clearly as test failures rather than teardown errors.🐛 Proposed fix to handle thread timeouts
threads = [threading.Thread(target=_create_schema) for _ in range(2)] for thread in threads: thread.start() for thread in threads: thread.join(timeout=10) + if thread.is_alive(): + raise TimeoutError("Schema creation thread timed out and may be deadlocked") assert not errors, errors📝 Committable suggestion
🤖 Prompt for AI Agents