[Pdns-users] stuck tcp sessions on recursor
spork at bway.net
Thu Feb 24 20:06:12 UTC 2011
On Thu, 24 Feb 2011, bert hubert wrote:
> On Thu, Feb 24, 2011 at 01:33:24PM -0500, Charles Sprickman wrote:
>> "Simon Bedford, Brad Dameron and Laurient Papier discovered
>> relatively high TCP/IP loads could cause TCP/IP service to shut down
>> over time. Addressed in commits 1546, 1640, 1652, 1685, 1698.
>> Additional information provided by Zwane Mwaikambo, Nicholas Miell
>> and Jeff Roberson. Testing by Christian Hofstaedtler and Michael
>> I was scanning for "stuck in CLOSED" and similar stuff. I'll try
>> 3.3 and see how that goes, thanks!
> this definitely sounds like 3.3 material!
So far so good, nearly 500,000 tcp queries without any lingering sockets.
Totally unrelated, but I see a stat that's not mentioned in the docs:
"no-packet-error 492682". What is that, and is it any cause for concern?
I'm really happy with the recursor so far, we previously used dnscache and
we're seeing about 1/5 the cpu usage and I believe we're also answering
queries that we weren't before - our overall qps went up quite a bit after
More information about the Pdns-users