I tried using memcache.py for a long time. I got a lot of collisions. A simple get after a set (and replace) gives me incorrect key value pairs.<br>I tested cmemcache.py for over a day does not give this problem. But this "server sent data for key not in request" error just kills the process and this needs to be fixed.
<br>It will be great if someone can tell how to fix this problem of libmemcache.<br>thanks<br>mark<br><br><br><div><span class="gmail_quote">On 1/30/07, <b class="gmail_sendername">Philip Neustrom</b> <<a href="mailto:firstname.lastname@example.org">
email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
I've been having similar issues with cmemcache. I've also noticed<br>that it kills the process when it can't contact the memcached (or it<br>goes into an infinite loop). This is no doubt due to how it deals<br>
with libmemcache, which is logging/error-message heavy.<br><br>I saw an earlier email about some PHP bindings that wrapped<br>libmemcache that had similar issues, but it didn't go into much detail<br>about how stuff got fixed.
<br><br>For now I'm switching back to memcache.py..<br><br>--Philip Neustrom<br><br>On 1/30/07, mark <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br>> hi<br>> i am using cmemcached which is a python wrapper for libmemcache:
<br>> I get this fatal error message regularly:<br>><br>> [<a href="mailto:FATAL@1170222010.740685">FATAL@1170222010.740685</a>] mcm_fetch_cmd():1176: memcache(4) protocol error:<br>> server sent data for key not in request
<br>><br>> can you tell what i should do?<br>> thanks<br>> mark<br>><br></blockquote></div><br>