Here we go, better description of SO_LINGER … this rings a bell. Lets you set the time allowed for clean versus abrupt connection close. The side effect is that your connection structures can get cleaned up quicker.
Still looking for validation of Squid / Apache using this to manage poorly behaving clients. Matthew On Apr 3, 2014, at 11:10 AM, Sean Cribbs <[email protected]> wrote: > This is likely something you can tweak with sysctl. The HTTP interface > already has SO_REUSEADDR on. This may be of help: > > http://tux.hk/index.php?m=05&y=09&entry=entry090521-111844 > > > On Thu, Apr 3, 2014 at 10:02 AM, Sean Allen <[email protected]> > wrote: > We are using pre11 right now. > > When we open http connections, they hang around for a long time in CLOSE_WAIT > which results in really spiky performance. When the connections close, its > fast, then they build up again, > > Is there something that needs to be configured w/ riak to get it to reuse the > sockets and not sit in close wait? > > > -- > > Ce n'est pas une signature > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > > > > -- > Sean Cribbs <[email protected]> > Software Engineer > Basho Technologies, Inc. > http://basho.com/ > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
