2x Improvement requests for the storage migration endpoint
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
I have been using the storage migrate endpoint to switch from OCI storage to S3.
While it worked okay for small domains, when I hit a domain with more artifacts (160K), some flaws popped up.
- The migration running artifact by artifact is slow for big domain. Some concurrency might be helpful.
- The migration is currently "locking" the whole domain for the duration of it. Which for bigger domains becomes service affecting, not being able to perform anything for 24 hours for example.
I created this draft PR. Feel free to close it if you find the approach bad, it's just something that Claude suggested. https://github.com/pulp/pulpcore/pull/7807
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 reviewing the storage migrate endpoint and the linked draft PR #7807, which contains the proposed approach. Compare the current artifact-by-artifact migration and domain-wide locking behavior with the two requested improvements. Done means large-domain migrations support useful concurrency without blocking the entire domain for the full migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100