1. 25 Mar, 2020 3 commits
  2. 24 Mar, 2020 2 commits
  3. 23 Mar, 2020 6 commits
  4. 22 Mar, 2020 4 commits
  5. 21 Mar, 2020 2 commits
  6. 20 Mar, 2020 5 commits
  7. 19 Mar, 2020 5 commits
  8. 18 Mar, 2020 2 commits
  9. 17 Mar, 2020 4 commits
  10. 16 Mar, 2020 2 commits
    • Klaus Post's avatar
      fix: remote profile names and extension (#9145) · eeb5942b
      Klaus Post authored
      Remote profiles are not formatted correctly:
      
      ```
      profile-172.31.91.126_9000-cpu.pprof
      profile-172.31.91.126_9000-goroutines-before.txt
      profile-172.31.91.126_9000-goroutines.txt
      profiling-172.31.80.49_9000-cpu.pprof.pprof
      profiling-172.31.80.49_9000-goroutines-before.txt.pprof
      profiling-172.31.80.49_9000-goroutines.txt.pprof
      profiling-172.31.86.101_9000-cpu.pprof.pprof
      profiling-172.31.86.101_9000-goroutines-before.txt.pprof
      profiling-172.31.86.101_9000-goroutines.txt.pprof
      profiling-172.31.91.191_9000-cpu.pprof.pprof
      profiling-172.31.91.191_9000-goroutines-before.txt.pprof
      profiling-172.31.91.191_9000-goroutines.txt.pprof
      ```
      
      `profiling` -> `profile`, remove extra extension.
      eeb5942b
    • yeungc's avatar
      7ec904d6
  11. 15 Mar, 2020 1 commit
    • Harshavardhana's avatar
      fix: lock maintenance should honor quorum (#9138) · c9212819
      Harshavardhana authored
      The staleness of a lock should be determined by
      the quorum number of entries returning stale,
      this allows for situations when locks are held
      when nodes are down - we don't accidentally
      clear locks unintentionally when they are valid
      and correct.
      
      Also lock maintenance should be run by all servers,
      not one server, stale locks need to be run outside
      the requirement for holding distributed locks.
      
      Thanks @klauspost for reproducing this issue
      c9212819
  12. 14 Mar, 2020 4 commits