On Fri, 19 Sep 1997, Chris Caputo wrote:
The problem does not happen when the news server (inn) is just processing the incoming news flow. When it starts handling many readers, then the problem kicks in and gets worse the more busy it is.
I have an F230 running 4.0.3 that doesn't have any problems with NFS timeouts. The INN reader server is an Ultra-1 with 1GB of RAM and peaks around 350 readers. It also takes in a single feed from our newsfeeder server. They are both on a FDDI ring.
I was getting very poor response when it was first installed, but that was due to a misconfiguration with the overviews. nnrpd was looking in the wrong directory, and thus fell back to scanning the spool to generate overview records. Once that was remedied, the problems disappeared. Are you using NFSv2 and UDP? How big are your control.cancel and misc.jobs.offered spool directories?
/news/spool on tor-na2:/spool soft/intr/proto=udp/vers=2/remote on Mon Aug 25 16:19:47 1997 /news/spool/over.db on tor-na2:/overdb soft/intr/proto=udp/vers=2/remote on Mon Aug 25 16:19:47 1997