1. 19 Dec, 2018 1 commit
  2. 03 Dec, 2018 1 commit
    • Witold Krecicki's avatar
      Fetchlimit test: update softquota limit to 380. · a48ca15e
      Witold Krecicki authored
      In the test the quota is set to 400, and softquota to 90%*400=360.
      We first attach to quota, and then if we're above softquota we
      drop the oldest client. With new socket code and taskmgr it's
      parallel enough to create a race between multiple instances doing
      'attach to quota' and then 'drop oldest client' - making number
      of clients go over softquota. It's not a problem in real life, as
      it's just soft quota.
      a48ca15e
  3. 15 Nov, 2018 1 commit
  4. 06 Nov, 2018 1 commit
  5. 01 Mar, 2018 1 commit
    • Evan Hunt's avatar
      revise soft limit test · 86838b2a
      Evan Hunt authored
      - don't bail out of the loop if clients are exceeded, just count incidents
      - verbosely describe expectations and results
      86838b2a
  6. 23 Feb, 2018 2 commits
  7. 22 Feb, 2018 1 commit
  8. 27 Jun, 2016 1 commit
  9. 14 Jun, 2016 2 commits
  10. 09 Jul, 2015 2 commits
    • Tinderbox User's avatar
      update copyright notice / whitespace · f16a6bfb
      Tinderbox User authored
      f16a6bfb
    • Evan Hunt's avatar
      [master] DDoS mitigation features · 1479200a
      Evan Hunt authored
      3938.	[func]		Added quotas to be used in recursive resolvers
      			that are under high query load for names in zones
      			whose authoritative servers are nonresponsive or
      			are experiencing a denial of service attack.
      
      			- "fetches-per-server" limits the number of
      			  simultaneous queries that can be sent to any
      			  single authoritative server.  The configured
      			  value is a starting point; it is automatically
      			  adjusted downward if the server is partially or
      			  completely non-responsive. The algorithm used to
      			  adjust the quota can be configured via the
      			  "fetch-quota-params" option.
      			- "fetches-per-zone" limits the number of
      			  simultaneous queries that can be sent for names
      			  within a single domain.  (Note: Unlike
      			  "fetches-per-server", this value is not
      			  self-tuning.)
      			- New stats counters have been added to count
      			  queries spilled due to these quotas.
      
      			See the ARM for details of these options. [RT #37125]
      1479200a