github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

gitea dump causes database query_timeout exceeded #8973

New Issue
Open
opened 2025-11-02 08:24:29 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 08:24:29 -06:00
Owner
Copy Link

Originally created by @FlyingOnion on GitHub (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

Originally created by @FlyingOnion on GitHub (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
GiteaMirror added the type/bug label 2025-11-02 08:24:29 -06:00
GiteaMirror commented 2025-11-02 08:24:29 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 19, 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 ....

@wxiaoguang commented on GitHub (May 19, 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 ....
GiteaMirror commented 2025-11-02 08:24:30 -06:00
Author
Owner
Copy Link

@supermangithu commented on GitHub (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)

@supermangithu commented on GitHub (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: * https://github.com/go-gitea/gitea/issues/19640 * https://github.com/go-gitea/gitea/issues/19593 * https://github.com/go-gitea/gitea/issues/19084 * https://github.com/go-gitea/gitea/issues/19640 * https://github.com/go-gitea/gitea/issues/19699 all about gitea dump ,transfer big sql database (backup mode)
GiteaMirror commented 2025-11-02 08:24:30 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 20, 2022):

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

@lunny commented on GitHub (May 20, 2022): 470K? There are really so many users? Is that a production system?
GiteaMirror commented 2025-11-02 08:24:30 -06:00
Author
Owner
Copy Link

@supermangithu commented on GitHub (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!

@supermangithu commented on GitHub (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!
GiteaMirror commented 2025-11-02 08:24:30 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (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.

@lunny commented on GitHub (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.
GiteaMirror commented 2025-11-02 08:24:30 -06:00
Author
Owner
Copy Link

@FlyingOnion commented on GitHub (May 24, 2022):

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

@FlyingOnion commented on GitHub (May 24, 2022): Then what about adding a `--skip-database` flag to `gitea dump` ?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8973
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?