Skip to content

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

Open
FlyingOnion opened this issue May 19, 2022 · 6 comments
Open

gitea dump causes database query_timeout exceeded #19752

FlyingOnion opened this issue May 19, 2022 · 6 comments
Labels

Comments

@FlyingOnion
Copy link

FlyingOnion commented May 19, 2022

Description

Database: mysql
Num of users: about 470k

Run gitea dump.

2022/05/19 14:36:18 cmd/dump.go:150:fatal() [F] Failed to dump database: Error 1907: Query execution was interrupted, query_timeout exceeded

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

@wxiaoguang
Copy link
Contributor

A little off-topic: I think the gitea dump isn't designed for large git site, indeed there are various problems when using the gitea dump (some are already reported in the issue list ....)

If you are running a large git site, you should have your own DevOps methods for backups ....

@supermangithu
Copy link

supermangithu commented May 20, 2022

A little off-topic: I think the gitea dump isn't designed for large git site, indeed there are various problems when using the gitea dump (some are already reported in the issue list ....)

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.
It need main developer and fundamental developer make a meeting to discuss and decide @lunny
and main developer paticipant @wxiaoguang .
Thanks in advance!
Look at these:

all about gitea dump ,transfer big sql database (backup mode)

@lunny
Copy link
Member

lunny commented May 20, 2022

470K? There are really so many users? Is that a production system?

@supermangithu
Copy link

supermangithu commented May 21, 2022

470K? There are really so many users? Is that a production system?

Glad to see you reply @lunny .
Suggestion:
the following link is similar to what i mentioned. He is migrating gitea repo to gitea repo #19533 ,my qusetion #19593 use giea dump to export and transfer code to another gitea instance.Gitea dump export function need more stability.
Thanks in advance!

@lunny
Copy link
Member

lunny commented May 21, 2022

I think you could do that with some other tools like rsync and some database hot back up tools yourselves. We should update the documentation about which content should be back up.

@FlyingOnion
Copy link
Author

FlyingOnion commented May 24, 2022

Then what about adding a --skip-database flag to gitea dump ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants