Skip to content
Snippets Groups Projects
  1. Dec 11, 2023
    • Will Chandler's avatar
      Restart Gitaly when updating Gitlab-Shell token · 05c8442762e4
      Will Chandler authored
      Originally Gitaly would shell out to Gitlab-Shell to make internal API
      calls. This had no retained state regarding the secret token, so no
      service restarts were required in this scenario.
      
      However, for several years the main Gitaly process has been responsible
      for calling the internal API. This will only read the Gitlab-Shell
      secret file during its startup process, and subsequent changes to that
      will not be detected by Gitaly, leading to spurious 401 errors.
      
      To resolve this, restart the Gitaly service when updating
      `gitlab_shell['secret_token']`.
      
      Changelog: fixed
      05c8442762e4
  2. Dec 12, 2023
  3. Dec 07, 2023
  4. Dec 12, 2023
  5. Dec 01, 2023
  6. Dec 12, 2023
  7. Dec 11, 2023
  8. Dec 05, 2023
    • Will Chandler's avatar
      Run gitaly with 'serve' subcommand · c012732c96af
      Will Chandler authored
      Gitaly has added several subcommands over the last few years.
      Execute Gitaly using the `serve` subcommand, rather then without a
      subcommand, which implicitly calls `serve`.
      
      Changelog: changed
      c012732c96af
    • Will Chandler's avatar
      Add 'use_wrapper' setting to Gitaly · 77c9b1eb7559
      Will Chandler authored
      Gitaly is in the process of implementing a write-ahead log (WAL) for git
      operations, which will provide significant benefits for resiliance and
      scalability.
      
      This model requires that we have only one Gitaly process running at a
      time. However, our current upgrade method keeps the old and new Gitaly
      processes running in parallel for an period of time defined by the
      administrator.
      
      The `gitaly-wrapper` binary is used by Omnibus to provide a stable pid
      to `runit` and sets the `GITALY_UPGRADES_ENABLED` environment variable
      that causes Gitaly to perform upgrades with concurrent processes.
      
      To prepare for the deployment of Gitaly's WAL architecture, add a new
      `gitaly['use_wrapper']` option which allows admins to execute Gitaly
      without the `gitaly-wrapper` binary so that there is never more than one
      Gitaly process running at once. This is enabled by default, admins must
      opt into the new behavior.
      
      Without the wrapper, sending SIGHUP to Gitaly will cause momentary
      service interruptions for git clone operations, ~300ms in our
      benchmarks. Read-only web requests will retry automatically for outages
      lasting up to 750ms and will handle the upgrade gracefully.
      
      We retain the wrapper for Praefect as this will remain compatible with
      running concurrent processes.
      
      Changelog: added
      77c9b1eb7559
  9. Dec 09, 2023
  10. Dec 04, 2023
  11. Nov 23, 2023
  12. Dec 08, 2023
  13. Dec 07, 2023
  14. Dec 08, 2023
  15. Dec 07, 2023
  16. Dec 08, 2023
  17. Dec 07, 2023
  18. Dec 05, 2023
  19. Dec 07, 2023
  20. Dec 06, 2023
  21. Dec 05, 2023
Loading