GitLab server stability

We have a fairly large number of developers, used to work in a central repo mode with frequent concurrent file-based commits, so i running ‘stress tests’ on our GitLab instance to make sure it can withstand the load (aka ‘drinking out of a firehose’).

I just ran a script that created 1000 tags in a local repository and then executed a push --all --follow-tags, upon which received a message (about 1.5 min into it): fatal: The remote end hung up unexpectedly; Everything up-to-date, and the script exited. Now I see Tags: 1000 tab reported on the Project’s Commits summary page, but only a few tags from a previous operation are actually listed when i click on that tab.

Trying to fetch to my local repo, says Already up-to-date.

Anyone seen that kind of an issue before, is there a way for me to recover from it, i.e. some sort of a sync between the remote repo and what’s displayed on the Web UI?

update: after i attempted to remove the tags with a different GitLab login creds, all my push’s were rejected, however the server somehow recovered and now displays all of the 1000 tags that i created earlier.

another update: crashed again (after i deleted all 1000 tags and reran) in about the same spot:

Total 1000 (delta 982), reused 0 (delta 0)
error: RPC failed; result=18, HTTP code = 200
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly

now, i again see the Tags: 1000 tab but no tags in it.

any ideas?