GItLab steht Donnerstag zwischen 12:30 und 14:30 Uhr aufgrund von Wartungsarbeiten nicht zur Verfügung.

  • Bob Van Landuyt's avatar
    Move the circuitbreaker check out in a separate process · f1ae1e39
    Bob Van Landuyt authored
    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.
    f1ae1e39
Name
Last commit
Last update
..
background_jobs Loading commit data...
bundle Loading commit data...
changelog Loading commit data...
check Loading commit data...
daemon_with_pidfile Loading commit data...
mail_room Loading commit data...
parallel-rsync-repos Loading commit data...
pkgr_before_precompile.sh Loading commit data...
rails Loading commit data...
rake Loading commit data...
rspec Loading commit data...
rspec-stackprof Loading commit data...
setup Loading commit data...
spinach Loading commit data...
spring Loading commit data...
storage_check Loading commit data...
upgrade.rb Loading commit data...
web Loading commit data...
with_env Loading commit data...