-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
gitea dump causes database query_timeout exceeded #19752
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
Comments
A little off-topic: I think the If you are running a large git site, you should have your own DevOps methods for backups .... |
This is what i mentioned before for gitea dump export about 100GB files is slow and not safe.I suggest gitea own three kinds of backup modes before.Gitea is all right for do the git version archive with small memory.On the contray, Gitlab CE need the high memory.
all about gitea dump ,transfer big sql database (backup mode) |
470K? There are really so many users? Is that a production system? |
Glad to see you reply @lunny . |
I think you could do that with some other tools like |
Then what about adding a |
Description
Database: mysql
Num of users: about 470k
Run
gitea dump
.The last row of dumped gitea-db is an
INSERT INTO user
statement.Gitea Version
1.15.5
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Helm chart
Database
MySQL
The text was updated successfully, but these errors were encountered: