Opened 8 years ago

Closed 7 years ago

#1323 closed defect (worksforme)

Missing zones

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

Description

I loaded a large zone into the sqlite3 database (cz.) and set a slave server to refresh from it every second. So it sent a request for SOA every second.

After few successful queries, bind10 reported that the cz. zone does not exist (sorry, I don't have the exact logs :-(). The next query took quite some time to answer, but it succeeded.

I have two theories what might have happened. Either the hotspot cache got flushed and there came a query, before it got answered, another one came and the DB was locked, so the second one answered immediately as not-exist.

The other is similar. I opened the DB with sqlite3, so maybe it got locked for quite a long time.

However, both should probably be SERVFAIL, instead of pretending not to be authoritative for the zone.

This might solve itself by switching to the new datasources, or might not.

Subtickets

Change History (4)

comment:1 Changed 8 years ago by shane

  • Defect Severity changed from N/A to High
  • Milestone changed from New Tasks to Year 3 Task Backlog

comment:2 Changed 7 years ago by jreed

  • Milestone set to Next-Sprint-Proposed

This issue should be checked again. (Note that hot spot cache was removed.)

comment:3 Changed 7 years ago by shane

  • Owner set to vorner
  • Status changed from new to assigned

comment:4 Changed 7 years ago by vorner

  • Resolution set to worksforme
  • Status changed from assigned to closed

This exact problem seems to be gone. I tried to load the server with SOA
queries. None of them said the zone is missing.

When I tried to make the database locked (by running b10-loadzone into the
database), it returned SERVFAIL, which is correct regarding this ticket (but
not desirable by admin, I'll open a different ticket for this).

Note: See TracTickets for help on using tickets.