Hi all,
Since upgrading to 8.X release of gitlab, I experience a lot of problems
with the jobs system, the full story is available here:
https://gitlab.com/gitlab-org/gitlab-ce/issues/3661
(I have been a happy user of gitlab for 2 years, I am even superhappy
with the neat integration of gitlab-ci in the 8.X releases, but now the
issue we face make the current users of our instance of gitlab unhappy,
which is a bad publicity for gitlab itself. I really need to find a fix
or a workaround.)
I tried to dig out the origin of the problem with some colleagues.
The only thing we could notice is that sidekiq processes just sleep when
our jobs are stalled.
It looks to me like a race condition, which happens typically when our
students fork projects (they more or less all do it at the same time).
But it also happens when people are simply working (pushing code to
their repository).
The consequence of those jobs not being executed is that the web pages
are not updated, and the builds are not performed.
I had to restart gitlab twice yesterday in the afternoon to let the
student complete their lab exercices.
I update our gitlab instance each month, manuallly (from source).
If I make an error during the process, I usually notice it quickly :-)
I wonder if there is someone around quite familiar with sidekiq and
gitlab who could help us to go further in the diagnostic of that problem.
Regards,
Daniel
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/gitlabhq/569F8DE7.2000509%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
