debian-mirror-gitlab/app/views/admin/application_settings/_gitaly.html.haml

25 lines
1.3 KiB
Text
Raw Normal View History

2019-09-30 21:07:59 +05:30
= form_for @application_setting, url: preferences_admin_application_settings_path(anchor: 'js-gitaly-settings'), html: { class: 'fieldset-form' } do |f|
2018-05-09 12:01:36 +05:30
= form_errors(@application_setting)
%fieldset
.form-group
2018-11-18 11:00:15 +05:30
= f.label :gitaly_timeout_default, 'Default Timeout Period', class: 'label-bold'
2018-11-08 19:23:39 +05:30
= f.number_field :gitaly_timeout_default, class: 'form-control'
.form-text.text-muted
Timeout for Gitaly calls from the GitLab application (in seconds). This timeout is not enforced
for git fetch/push operations or Sidekiq jobs.
2018-05-09 12:01:36 +05:30
.form-group
2018-11-18 11:00:15 +05:30
= f.label :gitaly_timeout_fast, 'Fast Timeout Period', class: 'label-bold'
2018-11-08 19:23:39 +05:30
= f.number_field :gitaly_timeout_fast, class: 'form-control'
.form-text.text-muted
Fast operation timeout (in seconds). Some Gitaly operations are expected to be fast.
If they exceed this threshold, there may be a problem with a storage shard and 'failing fast'
can help maintain the stability of the GitLab instance.
2018-05-09 12:01:36 +05:30
.form-group
2018-11-18 11:00:15 +05:30
= f.label :gitaly_timeout_medium, 'Medium Timeout Period', class: 'label-bold'
2018-11-08 19:23:39 +05:30
= f.number_field :gitaly_timeout_medium, class: 'form-control'
.form-text.text-muted
Medium operation timeout (in seconds). This should be a value between the Fast and the Default timeout.
2018-05-09 12:01:36 +05:30
= f.submit 'Save changes', class: "btn btn-success"