Commit graph

8 commits

Author SHA1 Message Date
GitLab Bot
833d57e60d Add latest changes from gitlab-org/gitlab@master 2020-07-08 15:09:24 +00:00
GitLab Bot
2c89e16976 Add latest changes from gitlab-org/gitlab@master 2020-02-12 15:09:37 +00:00
GitLab Bot
3ad11f24ca Add latest changes from gitlab-org/gitlab@master 2019-12-22 09:07:51 +00:00
GitLab Bot
9763c08170 Add latest changes from gitlab-org/gitlab@master 2019-12-17 03:07:45 +00:00
GitLab Bot
175b4fa261 Add latest changes from gitlab-org/gitlab@master 2019-12-11 18:08:10 +00:00
Qingyu Zhao
b7ea4bd853 Enable puma by default in GDK
Two changes:
1. Move bin/web to bin/web_unicorn(removed PUMA switching logic)
Introduce new shadow script bin/web. Now we have 3 scripts working
together: bin/web, bin/web_puma, bin/web_unicorn

  In bin/web, it checks ENV['USE_WEB_SERVER']:
    - if value is 'puma' or value is not set, call bin/web_puma
    - if value is 'unicorn', call bin/web_unicorn
    - report error if other values given

2. Gitlab rails allow ENV setting to override timeout
    - ENV['GITLAB_RAILS_RACK_TIMEOUT'] for service_timeout
    - ENV['GITLAB_RAILS_WAIT_TIMEOUT'] for wait_timeout
2019-07-09 23:31:32 +10:00
Jan Provaznik
d3a7bdda98 Moved RackTimeout observer to a different location
Because there will be similar observer for PumaWorkerKiller,
it makes sense to keep both on better place.
2019-06-12 12:09:04 +02:00
Jan Provaznik
6d6bae66df Added rack-timeout for Puma
It assures that requests are aborted after 60 seconds, otherwise
an exception is raised. This exception is logged by Sentry, also
there is a Prometheus counter for measuring number of requests in each
state.
2019-05-29 18:53:44 +00:00