Migration 0156_alter_contentartifact_relative_path_and_more.py fails on a big deployment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Version
3.117.0
Describe the bug
The 0156_alter_contentartifact_relative_path_and_more.py migration fails to finish running on our large deployment. The database gets into a deadlock and the migration process fails. This happens over and over again as our deployment tries to run the migrations again.
The production DB is 8.5TB in size.
In our stage instance this migration finished in 40 minutes. That DB is 300GB.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading 0156_alter_contentartifact_relative_path_and_more.py and reviewing the issue's deadlock reports. Compare its behavior on the 300GB stage database with the 8.5TB production deployment, then determine what allows the migration to complete reliably. Done means the migration finishes without leaving the database deadlocked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100