[Gitea] - Performance issues #153

Closed
opened 2021-10-13 08:46:49 +02:00 by muppeth · 5 comments
Owner

Looks like mostly du to the fallout of letsencrypt root cert change our instance is struggling with mirrors. It causes git to start ton of workers that timeout while waiting for repsonse from servers with outdated certs.

Looks like mostly du to the fallout of letsencrypt root cert change our instance is struggling with mirrors. It causes git to start ton of workers that timeout while waiting for repsonse from servers with outdated certs.
muppeth added the
bug
forgejo
labels 2021-10-13 08:46:49 +02:00
Author
Owner

I have disabled mirror feature for now, and I think we should keep it that way. Codeberg seem to get to the same conclusion:
https://blog.codeberg.org/mirror-repos-easily-created-consuming-resources-forever.html

I have disabled mirror feature for now, and I think we should keep it that way. Codeberg seem to get to the same conclusion: https://blog.codeberg.org/mirror-repos-easily-created-consuming-resources-forever.html
muppeth added the
Urgent!
label 2021-10-13 08:52:26 +02:00
Owner

Can we close this? I don't think it is a problem anymore...

Can we close this? I don't think it is a problem anymore...
Author
Owner

Yes. Seems like the problematic git instance has upgraded their certs and things are back to normal.

Yes. Seems like the problematic git instance has upgraded their certs and things are back to normal.

Codeberg seem to get to the same conclusion:

Last time I checked Codeberg had Push mirrors.

>> Codeberg seem to get to the same conclusion: Last time I checked Codeberg had Push mirrors.
Author
Owner

@ultimate thanks I will have a look. Althogh the issue is now gone because of the letsencrypt havoc over on most instances, I do fear gigantic littering and abuse. I will have a look at push only possibility.

@ultimate thanks I will have a look. Althogh the issue is now gone because of the letsencrypt havoc over on most instances, I do fear gigantic littering and abuse. I will have a look at push only possibility.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Disroot-Project#153
No description provided.