Skip to content
Snippets Groups Projects
  1. Jun 01, 2022
  2. May 27, 2022
    • Balasankar "Balu" C's avatar
      Skip auto-restart of PG during reconfigure as part of pg-upgrade · 0cdbc747
      Balasankar "Balu" C authored
      
      In nodes where Geo PG runs along with regular PG, during the PG upgrade
      process of regular PG, a reconfigure is initiated. This reconfigure will
      update the `VERSION` file in Geo PG's directory also with the new
      verison information and trigger a restart of the Geo PG. However,
      because Geo PG's data is still of the old version but the binaries have
      already been updated to point to the new version, this restart will fail
      due to mismatch.
      
      Because PG upgrade anyways causes the DB to be stopped and started, we
      can safely skip the automatic restart as part of reconfigure and avoid
      this failure.
      
      Changelog: fixed
      Signed-off-by: default avatarBalasankar "Balu" C <balasankar@gitlab.com>
      0cdbc747
  3. Jun 01, 2022
  4. May 31, 2022
  5. May 30, 2022
  6. May 19, 2022
  7. May 30, 2022
  8. May 27, 2022
  9. May 23, 2022
  10. May 27, 2022
  11. May 25, 2022
  12. May 03, 2022
  13. May 25, 2022
  14. May 16, 2022
    • Patrick Steinhardt's avatar
      gitaly: Remove configuration for Rugged's gitconfig search path · 517a05bf
      Patrick Steinhardt authored
      Gitaly is still using Rugged in its Ruby sidecar to provide a very
      limited set of RPCs that have not yet been ported to Go. While Rugged in
      the past required the gitconfig file to function correctly, nowadays it
      only requires the `core.fsyncObjectFiles` config entry. This entry must
      be set to `true` or otherwise it is trivial to end up with repository
      corruption.
      
      This means that the gitconfig must be in a specific well-known state for
      Rugged to operate correctly. But currently there is still the option to
      set Rugged's gitconfig search path, which must in fact point to a path
      that contains a gitconfig with the mentioned config entry. This is quite
      fragile without any benefit for the administrator at all.
      
      To fix this, Gitaly has introduced a fallback mode via [1] that causes
      it to write a Rugged-specific gitconfig file in case the Rugged search
      path is not set up. This allows us to now phase out support for setting
      this configuration altogether: it's not required, may cause repository
      corruption if misconfigured, and ultimately only makes the architecture
      harder to reason about given that we currently share this gitconfig file
      between multiple components.
      
      Remove the ability to set Rugged's gitconfig search path without any
      replacement.
      
      [1]: https://gitlab.com/gitlab-org/gitaly/-/merge_requests/4560
      
      Changelog: removed
      517a05bf
  15. May 24, 2022
  16. May 23, 2022
  17. May 17, 2022
Loading