9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] continued dns problems
Date: Sun, 18 Apr 2010 20:31:19 -0400	[thread overview]
Message-ID: <f2c8825311e53e096979d1824a06cb3b@kw.quanstro.net> (raw)

disclaimer: dns works great at 2 of the 3 plan 9 sites i maintain.
unfortunately, one squeeky mouse gets the exterminator fired.

dns under heavy use is continuing to be problematic.  before
the recent locking changes, i was seeing several crashes a month.
after the locking changes, i am seeing many bad rrs that appear
to cause lookups to fail.  the changes all looked good to me, so
i'm uncertain what's going on.  regardless, there were 6-7 *reported*
lookup failures on friday.  i don't know if the crashes were masking
the old problem. google.com, for example,  tends to get a number
of wierd rrs. pages don't load.

bowing to pressure over failed lookups, i'm trying a downgrade to
the server as of 20100305.  i'm hoping i can more easily detect a
broken server than one with bad rrs.

sorry for the crappy bug report.  there has been zero time in the
schedule to debug this problem.  (and people don't generally
even report a problem.)  i'm also sorry that there's no code, but
it's not clear to me that change is welcome.

despite russ' objections, i still think ndb/dns needs a restructuring.
if the rr db were a single thread that communicated with the
query threads via channels, it would be much easier to debug.

after at least 10 years of the current setup, we've proven that
the current structure is at a minimum hard to debug.

- erik



             reply	other threads:[~2010-04-19  0:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19  0:31 erik quanstrom [this message]
2010-04-22 17:08 ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f2c8825311e53e096979d1824a06cb3b@kw.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).