1. 16 8月, 2018 1 次提交
  2. 15 8月, 2018 2 次提交
  3. 14 8月, 2018 4 次提交
  4. 13 8月, 2018 4 次提交
  5. 11 8月, 2018 2 次提交
  6. 10 8月, 2018 6 次提交
  7. 09 8月, 2018 9 次提交
  8. 08 8月, 2018 1 次提交
    • Æ
      Add ability suppress the global "You won't be able [use] SSH" message · b6ba8cc6
      Ævar Arnfjörð Bjarmason 提交于
      This fixes gitlab-org/gitlab-ce#49953, as noted in the documentation
      this feature is intended to be used when SSH certificates are
      enabled. Then this warning becomes not only pointless, but also
      misleading.
      
      This builds on top of gitlab-org/gitlab-ce!21009 since both need to
      modify the same documentation, which avoids a merge conflict.
      
      See also the gitlab-org/gitlab-ce#49218 issue and associated merge
      request.
      b6ba8cc6
  9. 07 8月, 2018 9 次提交
  10. 06 8月, 2018 1 次提交
    • Y
      Respond to DB health in background migrations · 91b752dc
      Yorick Peterse 提交于
      This changes the BackgroundMigration worker so it checks for the health
      of the DB before performing a background migration. This in turn allows
      us to reduce the minimum interval, without having to worry about blowing
      things up if we schedule too many migrations.
      
      In this setup, the BackgroundMigration worker will reschedule jobs as
      long as the database is considered to be in an unhealthy state. Once the
      database has recovered, the migration can be performed.
      
      To determine if the database is in a healthy state, we look at the
      replication lag of any replication slots defined on the primary. If the
      lag is deemed to great (100 MB by default) for too many slots, the
      migration is rescheduled for a later point in time.
      
      The health checking code is hidden behind a feature flag, allowing us to
      disable it if necessary.
      91b752dc
  11. 05 8月, 2018 1 次提交