Push --mirror large repos fail

How to Use GitLab Self-managed
1

I can’t “push --mirror” a large (1.3gb 750k commits) repository to my gitlab server . I’ve had to push it branch by branch. Which is really annoying

Setting unicorn['worker_timeout'] = 3600 hasn’t helped

Any advice on other values to tune.

This error is shown in gitlab-shell/gitlab-shell.log
24933:W, [2017-12-01T11:54:16.076835 #7732] WARN -- : Failed to connect to internal API <POST http://127.0.0.1:8080/api/v4/internal/allowed>: #<Net::ReadTimeout: Net::ReadTimeout>

Gitlab hosted on a 4core, 8GB machine

System information
System:		Ubuntu 16.04
Current User:	git
Using RVM:	no
Ruby Version:	2.3.5p376
Gem Version:	2.6.13
Bundler Version:1.13.7
Rake Version:	12.1.0
Redis Version:	3.2.5
Git Version:	2.13.6
Sidekiq Version:5.0.4
Go Version:	unknown

GitLab information
Version:	10.2.2
Revision:	da70bc4
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		https://redacted
HTTP Clone URL:	https://redacted
SSH Clone URL:	git@redacted
Using LDAP:	yes
Using Omniauth:	no

GitLab Shell
Version:	5.9.4
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
Hooks:		/opt/gitlab/embedded/service/gitlab-shell/hooks
Git:		/opt/gitlab/embedded/bin/git
2

Hi - did you ever get to the bottom of this issue. I am seeing similar errors in our environment and it ends up causing the system to become slow and finally unresponsive. I have a call logged with Gitlab support but would appreciate any direction whilst waiting on that. I’ll post up anything they find when available but have previously been told Gitlab is intelligent enough to manage the number of worker processes etc so haven’t amended anything there.

Thanks

Adam

3

No I never got to the bottom of the issue.