kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/app/controllers/admin/health_check_controller.rb

13 lines
430 B
Ruby
Raw Normal View History

Add health_check access token, and enforce on the health_check endpoint Also added a health check page to the admin section for resetting the token.
2016-05-09 19:21:22 -04:00
class Admin::HealthCheckController < Admin::ApplicationController
def show
Bump health_check gem to version 2.6.0
2017-03-03 13:44:08 -05:00
@errors = HealthCheck::Utils.process_checks(['standard'])
Add a Circuitbreaker for storage paths
2017-05-17 12:17:15 -04:00
@failing_storage_statuses = Gitlab::Git::Storage::Health.for_failing_storages
end
def reset_storage_health
Move the circuitbreaker check out in a separate process Moving the check out of the general requests, makes sure we don't have any slowdown in the regular requests. To keep the process performing this checks small, the check is still performed inside a unicorn. But that is called from a process running on the same server. Because the checks are now done outside normal request, we can have a simpler failure strategy: The check is now performed in the background every `circuitbreaker_check_interval`. Failures are logged in redis. The failures are reset when the check succeeds. Per check we will try `circuitbreaker_access_retries` times within `circuitbreaker_storage_timeout` seconds. When the number of failures exceeds `circuitbreaker_failure_count_threshold`, we will block access to the storage. After `failure_reset_time` of no checks, we will clear the stored failures. This could happen when the process that performs the checks is not running.
2017-11-13 10:52:07 -05:00
Gitlab::Git::Storage::FailureInfo.reset_all!
Add a Circuitbreaker for storage paths
2017-05-17 12:17:15 -04:00
redirect_to admin_health_check_path,
notice: _('Git storage health information has been reset')
Add health_check access token, and enforce on the health_check endpoint Also added a health check page to the admin section for resetting the token.
2016-05-09 19:21:22 -04:00
end
end
Copy permalink