1. 14 Oct, 2014 3 commits
  2. 08 Oct, 2014 3 commits
  3. 07 Oct, 2014 4 commits
  4. 06 Oct, 2014 6 commits
  5. 03 Oct, 2014 2 commits
  6. 02 Oct, 2014 5 commits
  7. 01 Oct, 2014 2 commits
  8. 30 Sep, 2014 2 commits
  9. 29 Sep, 2014 9 commits
  10. 24 Sep, 2014 1 commit
  11. 17 Sep, 2014 2 commits
  12. 16 Sep, 2014 1 commit
    • Ensure Eureka server gets iniialized with non-zero count · 191bad05
      Dave Syer authored
      The problem is pretty deep here so I hope I did something sane. Basically if
      PeerAwareInstanceRegistry.openForTraffic(int) ever gets called with a 0 argument
      it resets the threshold for numberOfRenewsPerMinThreshold to 0 from which
      it only ever recovers if the same method is called again with a non-zero argument.
      For a standalone server this means that it will never automatically expire
      any leases (only when it chats to its neighbours and finds out they have
      registered services will it ever switch the threshold back on).
      
      Another problem (unsolved) is that the reset mechanism will kick back in
      occasionally (resetting to 1 with this change, but that's probably also
      a bad thing). And when there *are* actually peers to talk to unless they are
      in AWS they will never communicate correctly about the actual number of local
      services (the criteria for that are deeply connected with AWS and EIP).
      
      Fixes gh-6