As it tuns out this is clearly not an issue. We have a machine here with 30,000 connections in TIME_WAIT and the admin of that machine said there is little or no performance issues until the number raises over 10,000. So my mere 400 seems quite pathetic really :) Thanks to all those that assisted me. I really appreciate it.
Best Regards Damien On Wed 17/09/08 6:18 AM , "Ted Dunning" [EMAIL PROTECTED] sent: > There are OS settings, but modern Linux kernels automatically adjust > the setting if necessary. > > On Tue, Sep 16, 2008 at 8:38 AM, Raghu Angadi wrote: > Thats ok. Its a normal TCP state for the closed connections. There > is probably some OS level setting to reduce the amount of time these > connections stay in this state. > It does not indicate a bug in application. > Raghu. > wrote: > Hi all, > We have a 10 node cluster and I noticed that there are a large > number of connections in TIME_WAIT status, over 400 to more precise. > Does anyone > else see so many unclosed connections or have I done something wrong > in my config. It appears to be coming from and going to other > datanodes. > I was running the javasort benchmark when I noticed it. Any advice > appreciated. > Regards > Damien > -- > ted > >
