An error occurred fetching the project authors.
  1. 19 Jun, 2019 1 commit
  2. 29 May, 2019 1 commit
  3. 03 May, 2019 1 commit
  4. 23 Apr, 2019 1 commit
  5. 05 Apr, 2019 1 commit
  6. 18 Mar, 2019 1 commit
  7. 14 Mar, 2019 1 commit
    • Ash McKenzie's avatar
      Tidy up Gitlab::Geo::HealthCheck · 044a695c
      Ash McKenzie authored
      Convert all to instance methods
      Remove redundant 'The ' from 'The Geo'
      Break out replication lag query into method
      Increase test coverage
      044a695c
  8. 24 Jan, 2019 1 commit
  9. 03 Aug, 2018 1 commit
  10. 24 Jul, 2018 1 commit
  11. 04 Jul, 2018 1 commit
  12. 03 Jul, 2018 1 commit
  13. 11 Jun, 2018 3 commits
  14. 04 Jun, 2018 1 commit
  15. 24 May, 2018 1 commit
  16. 01 May, 2018 1 commit
  17. 16 Apr, 2018 1 commit
  18. 06 Apr, 2018 1 commit
  19. 05 Apr, 2018 1 commit
  20. 03 Apr, 2018 1 commit
  21. 28 Mar, 2018 1 commit
  22. 09 Feb, 2018 1 commit
  23. 05 Feb, 2018 2 commits
  24. 01 Feb, 2018 2 commits
  25. 25 Jan, 2018 1 commit
  26. 12 Jan, 2018 2 commits
    • Stan Hu's avatar
      Allow Geo storage mismatch in a development environment · d56faabd
      Stan Hu authored
      If you want to run a Geo primary and secondary locally, your storage
      configuration should have the same names but different paths. This change
      loosens the check to ensure the names are the same.
      d56faabd
    • Stan Hu's avatar
      Gracefully handle case when no shard data is available · eb7df045
      Stan Hu authored
      It's possible that if the GeoNodeStatus fails to fetch, we might end
      up with a state where the primary loads the last known state without
      any shard information. In this case, we should just report "UNKNOWN"
      for the storage configuration match check.
      
      Relates to #4586
      eb7df045
  27. 10 Jan, 2018 1 commit
  28. 03 Jan, 2018 5 commits
  29. 21 Dec, 2017 1 commit
  30. 20 Dec, 2017 1 commit
  31. 13 Dec, 2017 1 commit