Opened 8 years ago

Closed 5 years ago

#1933 closed defect (wontfix)

very high load and bad performance with REFUSED

Reported by: jreed Owned by:
Priority: medium Milestone: DNS Outstanding Tasks
Component: b10-auth Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Medium
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 8 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

As seen in ticket #1932, all zones were refused due to an error in 1 out of 19 zones.

Thsi was a very busy server getting around 17000 packets per second. With one auth server it could only send out around 1300 packets per second. When I added seven other auth servers it could send out 2600 packets per second. (8 CPU system.)

The processes all had 100% CPU or very near.

In most cases, my queries resulted in timeouts or in refused.

Once the one zone was fixed and reconfigured (I set the file name to same file and ran config commit), the CPU load dropped to 33% for each b10-auth and the no more timeouts.

Subtickets

Change History (6)

comment:1 Changed 8 years ago by shane

  • Milestone changed from New Tasks to Next-Sprint-Proposed

comment:2 Changed 8 years ago by jinmei

This is in-memory zone, right? And while it was heavily busy, it simply returned REFUSED?

comment:3 follow-up: Changed 8 years ago by vorner

It just crossed my mind. If the config was rejected, the auth server used the
defaults. And the defaults are to use sqlite3 backend, right? So it looked into
the database every time to find out there's no zone.

This is just a guess.

comment:4 in reply to: ↑ 3 Changed 7 years ago by jinmei

Replying to vorner:

It just crossed my mind. If the config was rejected, the auth server used the
defaults. And the defaults are to use sqlite3 backend, right? So it looked into
the database every time to find out there's no zone.

This is just a guess.

I suspect that's the reason. If we cannot confirm it, can we close the ticket for now?

comment:5 Changed 6 years ago by stephen

  • Milestone set to DNS Outstanding Tasks

comment:6 Changed 5 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed

DNS and BIND10 framework is outside of scope for Kea project.
The corresponding code has been removed from Kea git repository.
If you want to follow up on DNS or former BIND10 issues, see
http://bundy-dns.de project.

Closing ticket.

Note: See TracTickets for help on using tickets.