Re: [Pdns-users] stuck tcp sessions on recursor

2011-02-28 Thread Charles Sprickman
On Thu, 24 Feb 2011, bert hubert wrote: On Thu, Feb 24, 2011 at 03:06:12PM -0500, Charles Sprickman wrote: this definitely sounds like 3.3 material! So far so good, nearly 500,000 tcp queries without any lingering sockets. Good! Totally unrelated, but I see a stat that's not mentioned in

[Pdns-users] stuck tcp sessions on recursor

2011-02-24 Thread Charles Sprickman
Howdy, I'm seeing an issue with tcp queries on powerdns recursor 3.2. We run two instances of pdns recursor on an internal network and it's mainly hit by lots of qmail delivery servers. They are doing a ton of lookups, I think we peak around 4000 queries/second. With more people using

Re: [Pdns-users] stuck tcp sessions on recursor

2011-02-24 Thread Kenneth Marshall
On Thu, Feb 24, 2011 at 01:20:13PM -0500, Charles Sprickman wrote: Howdy, I'm seeing an issue with tcp queries on powerdns recursor 3.2. We run two instances of pdns recursor on an internal network and it's mainly hit by lots of qmail delivery servers. They are doing a ton of lookups, I

Re: [Pdns-users] stuck tcp sessions on recursor

2011-02-24 Thread bert hubert
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

Re: [Pdns-users] stuck tcp sessions on recursor

2011-02-24 Thread Charles Sprickman
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,

Re: [Pdns-users] stuck tcp sessions on recursor

2011-02-24 Thread bert hubert
On Thu, Feb 24, 2011 at 03:06:12PM -0500, Charles Sprickman wrote: this definitely sounds like 3.3 material! So far so good, nearly 500,000 tcp queries without any lingering sockets. Good! Totally unrelated, but I see a stat that's not mentioned in the docs: no-packet-error 492682. What