debian-mirror-gitlab/config/puma.rb.example

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

103 lines
3.3 KiB
Text
Raw Normal View History

2019-07-31 22:56:46 +05:30
# frozen_string_literal: true
# Load "path" as a rackup file.
#
# The default is "config.ru".
#
rackup 'config.ru'
pidfile '/home/git/gitlab/tmp/pids/puma.pid'
state_path '/home/git/gitlab/tmp/pids/puma.state'
stdout_redirect '/home/git/gitlab/log/puma.stdout.log',
'/home/git/gitlab/log/puma.stderr.log',
true
# Configure "min" to be the minimum number of threads to use to answer
# requests and "max" the maximum.
#
# The default is "0, 16".
#
threads 1, 16
# By default, workers accept all requests and queue them to pass to handlers.
# When false, workers accept the number of simultaneous requests configured.
#
# Queueing requests generally improves performance, but can cause deadlocks if
# the app is waiting on a request to itself. See https://github.com/puma/puma/issues/612
#
# When set to false this may require a reverse proxy to handle slow clients and
# queue requests before they reach puma. This is due to disabling HTTP keepalive
queue_requests false
# Bind the server to "url". "tcp://", "unix://" and "ssl://" are the only
# accepted protocols.
bind 'unix:///home/git/gitlab/tmp/sockets/gitlab.socket'
workers 3
require_relative "/home/git/gitlab/lib/gitlab/cluster/lifecycle_events"
require_relative "/home/git/gitlab/lib/gitlab/cluster/puma_worker_killer_initializer"
on_restart do
# Signal application hooks that we're about to restart
2019-12-21 20:55:43 +05:30
Gitlab::Cluster::LifecycleEvents.do_before_master_restart
2019-07-31 22:56:46 +05:30
end
before_fork do
# Signal to the puma killer
Gitlab::Cluster::PumaWorkerKillerInitializer.start @config.options unless ENV['DISABLE_PUMA_WORKER_KILLER']
# Signal application hooks that we're about to fork
Gitlab::Cluster::LifecycleEvents.do_before_fork
end
Gitlab::Cluster::LifecycleEvents.set_puma_options @config.options
on_worker_boot do
# Signal application hooks of worker start
Gitlab::Cluster::LifecycleEvents.do_worker_start
end
2023-01-13 00:05:48 +05:30
on_worker_shutdown do
# Signal application hooks that a worker is shutting down
Gitlab::Cluster::LifecycleEvents.do_worker_stop
end
2019-07-31 22:56:46 +05:30
# Preload the application before starting the workers; this conflicts with
# phased restart feature. (off by default)
preload_app!
tag 'gitlab-puma-worker'
# Verifies that all workers have checked in to the master process within
# the given timeout. If not the worker process will be restarted. Default
# value is 60 seconds.
#
worker_timeout 60
2020-01-01 13:55:28 +05:30
2021-03-08 18:12:59 +05:30
# https://github.com/puma/puma/blob/master/5.0-Upgrade.md#lower-latency-better-throughput
2021-06-08 01:23:25 +05:30
wait_for_less_busy_worker ENV.fetch('PUMA_WAIT_FOR_LESS_BUSY_WORKER', 0.001).to_f
2021-03-08 18:12:59 +05:30
2023-07-09 08:55:56 +05:30
# nakayoshi_fork was removed in Puma 6.0: https://github.com/puma/puma/issues/2258
2021-03-08 18:12:59 +05:30
# https://github.com/puma/puma/blob/master/5.0-Upgrade.md#nakayoshi_fork
2023-07-09 08:55:56 +05:30
if Gem::Version.new(Puma::Const::PUMA_VERSION).canonical_segments.first == 5 &&
ENV['DISABLE_PUMA_NAKAYOSHI_FORK'] != 'true'
nakayoshi_fork
end
2021-03-08 18:12:59 +05:30
2020-01-01 13:55:28 +05:30
# Use json formatter
require_relative "/home/git/gitlab/lib/gitlab/puma_logging/json_formatter"
json_formatter = Gitlab::PumaLogging::JSONFormatter.new
log_formatter do |str|
json_formatter.call(str)
2021-03-08 18:12:59 +05:30
end
2021-10-27 15:23:28 +05:30
lowlevel_error_handler do |ex, env|
if Raven.configuration.capture_allowed?
Raven.capture_exception(ex, tags: { 'handler': 'puma_low_level' }, extra: { puma_env: env })
end
# note the below is just a Rack response
[500, {}, ["An error has occurred and reported in the system's low-level error handler."]]
end