Investigate multiple concurrently running git archive commands cause remote end hung up unexpectedly error

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

After updating our GitLab Server (installations with omnibus-gitlab) from 14.3.3 to 14.8.4 we have experienced that when we run multiple git archive commands in parallel the fetching fails.

After updating our GitLab Server again from 14.8.4 to 14.9.1 we have observed that it is possible to fetch more in parallel with git archive then before but the error still reoccurs.

What exactly causes this error? Are there any known limitations? Is there any configuration which modifies this behaviour?

Steps to reproduce

for i in {1..20}; do ( time git archive --format=tgz --prefix=<PREFIX> --remote=git@<GITLAB_SERVER>:<GROUP>/<REPO>.git <BRANCH> > $i.tgz &) ; done

The mentioned error is best reproduced with large repositories (several 100MB).

What is the current bug behavior?

After exactly one minute the git archive commands are aborted and the following error appears:

fatal: the remote end hung up unexpectedly

And most of the .tgz files are not fully downloaded.

What is the expected correct behavior?

The download of all files is complete and git archive commands are finished successfully.

Relevant logs and/or screenshots

gitlab-ctl.log

Results of GitLab environment info

Expand for output related to GitLab environment info

System information
System:         Ubuntu 20.04
Current User:   git
Using RVM:      no
Ruby Version:   2.7.5p203
Gem Version:    3.1.4
Bundler Version:2.2.33
Rake Version:   13.0.6
Redis Version:  6.2.6
Sidekiq Version:6.4.0
Go Version:     unknown

GitLab information
Version:        14.9.1
Revision:       5b713e1e9a3
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     12.7
URL:            https://
HTTP Clone URL: https:///some-group/some-project.git
SSH Clone URL:  git@:some-group/some-project.git
Using LDAP:     yes
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version:        13.24.0
Repository storage paths:
- default:      /usr/data/gitlab/git-data/repositories
GitLab Shell path:              /opt/gitlab/embedded/service/gitlab-shell

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=tru)
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 13.24.0 ? ... OK (13.24.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes
Number of Sidekiq processes (cluster/worker) ... 1/1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
User output sanitized. Found 100 users of 100 limit.
Checking LDAP ... Finished
Checking GitLab App ...
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units)
Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units)
Projects have namespace: ...
26/5 ... yes
26/6 ... yes
26/7 ... yes
26/8 ... yes
26/9 ... yes
26/10 ... yes
48/11 ... yes
42/13 ... yes
52/14 ... yes
41/15 ... yes
35/17 ... yes
50/19 ... yes
49/20 ... yes
42/21 ... yes
42/22 ... yes
26/28 ... yes
70/33 ... yes
70/35 ... yes
70/36 ... yes
70/37 ... yes
70/38 ... yes
70/39 ... yes
70/40 ... yes
70/41 ... yes
70/42 ... yes
70/43 ... yes
26/44 ... yes
70/46 ... yes
26/47 ... yes
26/48 ... yes
26/49 ... yes
26/50 ... yes
26/51 ... yes
26/52 ... yes
26/53 ... yes
70/55 ... yes
70/56 ... yes
70/57 ... yes
46/58 ... yes
63/59 ... yes
63/60 ... yes
63/61 ... yes
63/62 ... yes
63/63 ... yes
63/64 ... yes
63/65 ... yes
63/66 ... yes
63/67 ... yes
63/68 ... yes
63/69 ... yes
63/70 ... yes
63/71 ... yes
63/72 ... yes
64/73 ... yes
64/74 ... yes
77/75 ... yes
26/76 ... yes
49/77 ... yes
16/78 ... yes
63/79 ... yes
43/80 ... yes
82/81 ... yes
64/82 ... yes
70/83 ... yes
26/84 ... yes
26/85 ... yes
26/86 ... yes
26/87 ... yes
26/88 ... yes
26/89 ... yes
26/90 ... yes
26/91 ... yes
26/92 ... yes
26/93 ... yes
26/94 ... yes
26/95 ... yes
26/96 ... yes
26/97 ... yes
26/98 ... yes
26/99 ... yes
26/100 ... yes
26/101 ... yes
26/102 ... yes
26/103 ... yes
26/104 ... yes
26/105 ... yes
26/106 ... yes
26/107 ... yes
26/108 ... yes
26/109 ... yes
26/110 ... yes
26/111 ... yes
26/112 ... yes
26/113 ... yes
26/114 ... yes
26/115 ... yes
26/116 ... yes
64/118 ... yes
64/119 ... yes
70/121 ... yes
70/122 ... yes
26/123 ... yes
26/124 ... yes
26/125 ... yes
26/126 ... yes
Redis version >= 5.0.0? ... yes
Ruby version >= 2.7.2 ? ... yes (2.7.5)
Git user has default SSH configuration? ... yes
Active users: ... 218
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished