1. 17 Aug, 2018 1 commit
  2. 14 Aug, 2018 2 commits
  3. 13 Aug, 2018 4 commits
  4. 12 Aug, 2018 1 commit
  5. 10 Aug, 2018 5 commits
  6. 09 Aug, 2018 8 commits
  7. 08 Aug, 2018 3 commits
  8. 07 Aug, 2018 8 commits
  9. 06 Aug, 2018 2 commits
    • James Ramsay's avatar
      Fix typo and improve formatting · 8c0a7e09f0a0
      James Ramsay authored
      8c0a7e09f0a0
    • Yorick Peterse's avatar
      Respond to DB health in background migrations · cbfd8c00e473
      Yorick Peterse authored
      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.
      cbfd8c00e473
  10. 05 Aug, 2018 1 commit
  11. 03 Aug, 2018 3 commits
  12. 02 Aug, 2018 2 commits