This *should* be better in latest version of the client. Had a bug that fixed an internal conn leak. Try it and let me know.<br><br>gw<br><br><div><span class="gmail_quote">On 8/6/07, <b class="gmail_sendername">Eli Bingham
</b> <<a href="mailto:eli@pandora.com">eli@pandora.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hey memcached folks,
<br><br>We've encountered an odd production issue with the java memcached<br>client. This is occuring in a memcached cluster of 30 nodes running<br>server version 1.2.1, with java client version 1.5.1. I realize<br>
neither of these are the latest and greatest versions of the<br>respective software, but I see nothing as of yet in the change logs<br>to indicate that our problem would be solved by upgrading.<br><br>The issue is that when one or more server nodes go down and then
<br>later come back up, dead connections seem to persist in the client<br>connection pools for an indefinite period. We are aware of this<br>because we can see the memcached client SockIOPool class logging the<br>following error on some percentage of incoming requests (where "foo"
<br>is just the output of the socket's toString method and "bar" is the<br>host).<br><br>++++ socket in avail pool is not connected: foo for host: bar<br><br>The errors seem to (very very) slowly decrease over time, but a lot
<br>of them persist after 24 hours and the only remedy is to restart the<br>application JVMs running the memcached client. Note that while this<br>error is occuring, the memcached node that died and then restarted<br>seems to be getting a relatively normal volume of traffic.
<br><br>These are the settings we currently use on SockIOPool:<br><br>pool.setMinConn(5);<br>pool.setMaxConn(50);<br>pool.setInitConn(5);<br>pool.setSocketTO(1000);<br>pool.setSocketConnectTO(100);<br>pool.setFailover(false);
<br>pool.setFailback(true);<br>pool.setAliveCheck(false);<br><br>Any help would be greatly appreciated.<br><br>Eli Bingham<br>Senior Engineer<br>Pandora Media, Inc.<br></blockquote></div><br><br clear="all"><br>-- <br>Greg Whalin