Migration from GitHub fails with Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction #1323
Labels
No Label
bug
Codeberg
contribution welcome
docs
duplicate
enhancement
infrastructure
legal
licence / ToS
public relations
question
s/Gitea/Forgejo
s/Pages
s/Weblate
s/Woodpecker
security
service
spam
upstream
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Codeberg/Community#1323
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Comment
I tried to migrate a (rather big) https://github.com/wxWidgets/wxWidgets.git repository from GitHub for testing it on Codeberg but migration unfortunately failed with the error message in the subject (there are no further details).
I used a token for migration, if it matters, and I didn't delete the repository just in case there could be something useful for diagnosing this issue in it.
@VadZ I cannot support technically but wanted to contribute that I am happy to hear you consider migrating this interesting and busy (75k+ commits and counting) repository to code berg. Welcome!
To be perfectly honest, this was just the first exploratory step, we don't have any concrete plans for migrating from GitHub yet, but I'd like to have a solution if this turns out to be necessary.
My bad, I used the wrong word "migrating" (I guess because most services suggest that).
What I really meant was more like "porting".
This is very likely related to forgejo/forgejo#220
We fixed a number of deadlocks in the past and for others we improved performance and optimized queries to reduce the chances that they occur. I am currently not aware of any other deadlocks that occur often or persist, but this one could be.
@VadZ I recommend that you retry the migration once, avoiding the rush hour during european evenings (16 - 23 CEST). If it still fails, we'll have a closer look. Please give us a precise timestamp.
Thanks, do you mean to give the time when I'll start the migration in advance or the time when it happens? I could try launching the migration again this night (2-3 CEST), but I wouldn't necessarily know when exactly it stops.
Try to tell us afterwards. We can search a little bit in the logs, but the more precise the better.
Sorry, no precise time stamp because it was taking too long and I logged off, but after retrying the migration last night, it ended with
this time.
Relevant log output:
Not sure what to take out of this. Did it simply timeout?