sameersbn / sameersbn/docker-gitlab
Migrate gitlab 11.10.4 to gitlab 16.6.2 with mysql to postgresql
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hello Team,
I'm in the process of upgrading my GitLab instance from version 11.10.4 to 16.6.2. Currently, my GitLab 11.10.4 instance uses MySQL, but due to the lack of MySQL support in GitLab versions after 13, I'm planning to migrate to PostgreSQL.
I've set up a new GitLab instance on another server with PostgreSQL, and it seems to be working fine. However, when attempting to restore the database from MySQL to PostgreSQL using the pgloader service, I encounter a 500 error. The error log file is available here.
https://gist.github.com/rrpnarola/b1499b2729be56158a5d9dab8b5544ad
My current setup includes over 2000 projects, and the backup size exceeds 200GB. I'm seeking guidance on the proper steps to successfully complete this migration.
Any help or insights you can provide would be greatly appreciated.
Thank you.
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 with the linked error log and gist, then review the reported GitLab 11.10.4 to 16.6.2 migration setup using pgloader. Determine the supported migration steps from MySQL to PostgreSQL and verify them against the 500 error. Done means the database restores successfully for the described GitLab instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, mysql, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100