Large artifacts cause timeout when uploading from runner

Summary

Uploading artifacts of a large size to gitlab fails after 3 times due to timeout and then passes the build. The upload also takes a lot longer than you'd expect for uploading over the same vlan.

Steps to reproduce

Having a CI pipeline that generates a large file (10gb-15gb) and submits itself as an artifact for uploading.

What is the current bug behavior?

The ci runner (on the same local network and vlan as gitlab) fails to upload it's artifacts and continues to pass the build.

What is the expected correct behavior?

The runner shouldn't continually fail to upload the artifacts.

Relevant logs and/or screenshots

Uploading artifacts...
<artifact1>: found 1 matching files                  
<artifact2>: found 1 matching files          
WARNING: Failed to load system CertPool: crypto/x509: system root pool is not available on Windows 
ERROR: Uploading artifacts to coordinator... error  error=couldn't execute POST against https://<url>/api/v4/jobs/1547/artifacts?artifact_format=zip&artifact_type=archive&expire_in=1+week: Post https://<url>/api/v4/jobs/1547/artifacts?artifact_format=zip&artifact_type=archive&expire_in=1+week: net/http: timeout awaiting response headers id=1547 token=b6ytraYM
WARNING: Retrying...                               
ERROR: Uploading artifacts to coordinator... error  error=couldn't execute POST against https://<url>/api/v4/jobs/1547/artifacts?artifact_format=zip&artifact_type=archive&expire_in=1+week: Post https://<url>/api/v4/jobs/1547/artifacts?artifact_format=zip&artifact_type=archive&expire_in=1+week: net/http: timeout awaiting response headers id=1547 token=b6ytraYM
WARNING: Retrying...                               
ERROR: Uploading artifacts to coordinator... error  error=couldn't execute POST against https://<url>/api/v4/jobs/1547/artifacts?artifact_format=zip&artifact_type=archive&expire_in=1+week: Post https://<url>/api/v4/jobs/1547/artifacts?artifact_format=zip&artifact_type=archive&expire_in=1+week: net/http: timeout awaiting response headers id=1547 token=b6ytraYM
FATAL: invalid argument                            
Job succeeded

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:         Ubuntu 18.04
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.4.4p296
Gem Version:    2.7.6
Bundler Version:1.16.2
Rake Version:   12.3.1
Redis Version:  3.2.11
Git Version:    2.18.0
Sidekiq Version:5.1.3
Go Version:     unknown


GitLab information
Version:        11.3.0-ee
Revision:       4e822ace150
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
DB Version:     9.6.8
Elasticsearch:  no
Geo:            no
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers: google_oauth2


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

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab Shell ...

GitLab Shell version >= 8.3.3 ? ... OK (8.3.3)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
9/3 ... ok
9/4 ... ok
2/5 ... ok
2/6 ... ok
2/7 ... ok
2/10 ... ok
2/12 ... ok
2/13 ... ok
50/14 ... ok
2/15 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Sidekiq ...


Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Reply by email is disabled in config/gitlab.yml
Checking LDAP ...


LDAP is disabled in config/gitlab.yml


Checking LDAP ... Finished


Checking GitLab ...


Git configured correctly? ... yes
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
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
9/3 ... yes
9/4 ... yes
2/5 ... yes
2/6 ... yes
2/7 ... yes
2/10 ... yes
2/12 ... yes
2/13 ... yes
50/14 ... yes
2/15 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.4.4)
Git version >= 2.9.5 ? ... yes (2.18.0)
Git user has default SSH configuration? ... yes
Active users: ... 46
Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)


Checking GitLab ... Finished