Update to Gitlab 16.0.1 - Commits not shown for a long time

After updating to newest Gitlab 16.0.1 commits in merge requests are not shown directly after pushing them. It takes a long time (about 10 minutes) after the commit appears in the Gitlab frontend.

This behavior also takes place when I trigger a CI/CD job. The job is in pending state for several minutes before starting it.

Are there any known errors? Does anyone else face issues like this?

I am running v16.0.1-ee self hosted.

1 Like

We’re in exactly the same situation, closing and re-opening the MR seems to fetch the missing commits but still we can’t merge the MR.

I’ve seen that there are many jobs in the sidekiq job queues and found out that they are related to the advanced search (elasticsearch). So I deactivated the advanced search (under Admin area > Settings > Advanced Search) and the performance of new commits and CI/CD jobs was normal again.

Maybe a reindex of the advanced search caused this problem.

This is also affecting our self-hosted instance of Gitlab EE. We noticed it when we first upgraded to 16.0. Unfortunately, disabling ElasticSearch didn’t seem to help.

We have also noticed that our runners don’t seem to pick up jobs anymore either.

EDIT: We disabled ElasticSearch and avoided using Gitlab the rest of the day. Everything seemed to start working like nothing happened about 10-15 hours later. Perhaps it had to work through outstanding Sidekiq job queues or something.