HTTP 524 timeout error during project import to GitLab.com
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
There have been several customers reporting that about HTTP 524 timeout error when doing project import to GitLab.com.
Their export file size is well within the import size limit of 5GB.
Per @T4cC0re:
Hendrik Meyer:palm_tree: 7 days ago 520 and 524 are VERY distinct issues.
524 is a timeout from Cloudflare to our Origin. Meaning our backend thought for too long.
CF will buffer the uploads before sending them to us, so a faster connection does not do anything here.
I will check our Timeout setting in CF soon. We might need to increase that once more
520s can happen when we don't drain pods and it goes away while handling a response.
Steps to reproduce
This seem to happen intermittently; try importing a project that is less than 5GB onto GitLab.com.
Example Project
What is the current bug behavior?
Project import to GitLab.com failed with timeout error (524 error)
What is the expected correct behavior?
Project import to GitLab.com should be successful for export size less than 5GB.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com.
Possible workarounds
- Import workarounds for large repositories
- Reduce repository size
- Verify if the
Uploadsfolder in the export file take up a significant disk usage, consider manually removing dated images from the folder.