BigW Consortium Gitlab

  1. 21 Oct, 2016 1 commit
    • Re-organize queues to use for Sidekiq · 97731760
      Yorick Peterse authored
      Dumping too many jobs in the same queue (e.g. the "default" queue) is a
      dangerous setup. Jobs that take a long time to process can effectively
      block any other work from being performed given there are enough of
      these jobs.
      
      Furthermore it becomes harder to monitor the jobs as a single queue
      could contain jobs for different workers. In such a setup the only
      reliable way of getting counts per job is to iterate over all jobs in a
      queue, which is a rather time consuming process.
      
      By using separate queues for various workers we have better control over
      throughput, we can add weight to queues, and we can monitor queues
      better. Some workers still use the same queue whenever their work is
      related. For example, the various CI pipeline workers use the same
      "pipeline" queue.
      
      This commit includes a Rails migration that moves Sidekiq jobs from the
      old queues to the new ones. This migration also takes care of doing the
      inverse if ever needed. This does require downtime as otherwise new jobs
      could be scheduled in the old queues after this migration completes.
      
      This commit also includes an RSpec test that blacklists the use of the
      "default" queue and ensures cron workers use the "cronjob" queue.
      
      Fixes gitlab-org/gitlab-ce#23370
  2. 28 Apr, 2016 1 commit
    • Use 'exec' in Unicorn and Sidekiq launch scripts · 8a6776ca
      Jacob Vosmaer authored
      When running Unicorn or Sidekiq in the foreground this change removes
      an intermediate /bin/sh process. This makes process supervision in the
      GitLab Development Kit more reliable.
      
      This change does not affect Omnibus-GitLab (because there we do not
      use these launch scripts). Installations from source do use the launch
      scripts but for the standard GitLab init script this change will not
      make a difference.
      
      Custom installations using Upstart or Systemd may be affected however,
      because under certain configurations these systems count exactly how
      many forks happen during process startup, and we are reducing that
      number by one here.
  3. 15 Jan, 2016 1 commit
  4. 14 Jan, 2016 1 commit
  5. 03 Dec, 2015 1 commit
  6. 26 Aug, 2015 1 commit
  7. 19 Aug, 2015 1 commit
  8. 01 Apr, 2015 1 commit
  9. 10 Sep, 2014 1 commit
  10. 08 Sep, 2014 1 commit
  11. 04 Jul, 2014 3 commits
  12. 12 Jun, 2014 1 commit
  13. 27 May, 2014 1 commit
  14. 01 Apr, 2014 1 commit
  15. 20 Mar, 2014 2 commits
  16. 10 Feb, 2014 1 commit
  17. 22 Oct, 2013 1 commit
  18. 15 Oct, 2013 1 commit