umm...<br>$mc = new Memcache;<br>if (!$mc->connect('<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://127.0.0.1/" target="_blank">127.0.0.1</a>',11212)) { $mc->connect('<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://127.0.0.1/" target="_blank">
127.0.0.1</a>',11212); }<br>this would incur a loooot of lag for the client if the connection times out.. and since i am getting this error very frequently...<br><br>umm steven.. when u had similar problems.. what did u do to trace the source.. with some concrete proof that would satisfy the management.. .. i hope u undertsand.. ;)
<br><br>and did u experiance any improvement/changes with respect to the problem., between different versions.. if u ever switched forth between them...<br><br>another interesting thing that one of the devs told me was they when they used pconnect() they would get connection time out errors and when they used connect(), they would get the unknown error.....
<br><br><br><div><span class="gmail_quote"><br>On 5/25/06, <b class="gmail_sendername">Paul Querna</b> <<a href="mailto:chip@corelands.com">chip@corelands.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;">
timeless wrote:<br>> Reinis Rozitis wrote:<br>><br>>> $mc = new Memcache;<br>>> if (!$mc->connect('<a href="http://127.0.0.1">127.0.0.1</a>',11212)) {<br>>> $mc->connect('<a href="http://127.0.0.1">
127.0.0.1</a>',11212); }<br>><br>> In this case, if the memcached on <a href="http://127.0.0.1">127.0.0.1</a> never answers, you'll wait 2<br>> seconds before failing to get the connection?<br>><br>> To the list, is there a way to get sub-second connection timeouts?
<br>><br>> I'd kind of like to implement exactly this, but our memcached cluster is<br>> about 9 hosts, and if any one is down, it would cause executive-level<br>> despondancy if the site went from 0.5-second page render times to
<br>> 2.5-second page render times until we pulled the errant memcached<br>> instance out of the pool.<br><br>The trick is to store your list of memcache servers in a config file.<br>(Or some other configuration method)
<br><br>Then you have some other process that updates this config file if a<br>memcache server is down -- without changing the total size of the<br>memcacehe server array, thereby keeping the distribution of most items<br>
in the cache.<br><br>I do this with apr_memecache -- not sure how to do it on other client<br>libraries.<br><br>-Paul<br></blockquote></div><br><br clear="all"><br>-- <br>Regards<br>M Kamran Nisar,