memcached server loses set command when followed by quit

Kevin Dalley kevin at kelphead.org
Fri Feb 1 15:41:22 UTC 2008


Thanks.  I believe that I have solved the problem.  I'll try to  get the
changes together soon. The localhost issue was just a timing problem.


On Sun, 2008-01-27 at 19:47 -0800, Brian Aker wrote: 
> Hi!
> 
> I would really recommend testing localhost vs non-localhost for this.
> 
> Cheers,
> 	-Brian
> 
> On Jan 27, 2008, at 10:34 AM, Kevin Dalley wrote:
> 
> > This looks like a server problem to me.  Does anyone else want to  
> > offer
> > an opinion? I am running libmemcached unit tests, and in non-blocking
> > tests, this string is sent to the server, 1.2.4, running in "-v -v"
> > mode:
> >
> > "set foo 0 0 16\r\nwhen we sanitize\r\nquit\r\n"
> >
> > followed by a new connection with "add foo 0 0 16\r\nwhen we sanitize 
> > \r
> > \n"
> >
> > I expect that the set will succeed, followed by a connection closed,
> > then an unsuccessful add. Sometimes, this works, but often the set
> > disappears.
> >
> > This is what I see:
> >
> > <7 new client connection
> > <7 connection closed.
> > <7 new client connection
> > <7 add foo 0 0 16
> >> 7 STORED
> >
> >
> > This is on Linux, a Ubuntu box, 2.6.22, with memcached-1.2.4, which I
> > compiled.
> 
> --
> _______________________________________________________
> Brian "Krow" Aker, brian at tangent.org
> Seattle, Washington
> http://krow.net/                     <-- Me
> http://tangent.org/                <-- Software
> http://exploitseattle.com/    <-- Fun
> _______________________________________________________
> You can't grep a dead tree.
> 



More information about the memcached mailing list