sianla / memcached

Automatically exported from code.google.com/p/memcached
0 stars 0 forks source link

Memcached: 55: Client using the ascii protocol #282

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Start memcached with this parameter : memcached -d -vv -m 10000 -u memcache 
-l 127.0.0.1 -p 11211 -c 2048 -t 20 -s /tmp/memcached
2. Put data object via java process into memcached.
3. It will reproduce this issue on memcached log screen itself.

What is the expected output? What do you see instead?

set XXX-XXX-CACHE:1d41402abc4b2a76b9719d921986505191 1 0 394

What version of the product are you using? On what operating system: 1.4.7 
version of Memcached I am using.

Please provide any additional information below.

Please find log what I am having once I am trying to start 

<55 new auto-negotiating client connection
55: Client using the ascii protocol
<55 stats
<54 connection closed.
<55 connection closed.
<54 new auto-negotiating client connection
54: Client using the ascii protocol
<54 stats
<55 new auto-negotiating client connection
55: Client using the ascii protocol
<55 stats
<54 connection closed.
<55 connection closed.
<54 new auto-negotiating client connection
54: Client using the ascii protocol
<54 stats
<54 connection closed.
<54 new auto-negotiating client connection
54: Client using the ascii protocol
<54 stats
<54 connection closed.
<54 new auto-negotiating client connection
54: Client using the ascii protocol
<54 version
>54 VERSION 1.4.7
<54 connection closed.
<54 new auto-negotiating client connection
54: Client using the ascii protocol
<54 stats
<54 connection closed.
<54 new auto-negotiating client connection
54: Client using the ascii protocol
<54 stats
<54 connection closed.
<55 new auto-negotiating client connection
55: Client using the ascii protocol
<55 stats
<55 connection closed.
<54 new auto-negotiating client connection
54: Client using the ascii protocol
<54 stats
<54 connection closed.

Original issue reported on code.google.com by umashank...@eco-mail.com on 25 Jul 2012 at 8:55

GoogleCodeExporter commented 8 years ago
This isn't likely a bug with memcached. it's a problem with your client not 
being used correctly. If you need support, please mail the mailing list with 
details on what client you're using and example code which doesn't work.

Original comment by dorma...@rydia.net on 27 Jul 2012 at 9:20

GoogleCodeExporter commented 8 years ago
Hi, thanks for reply me. yet am fighting with same issue, am trying to put data 
into memcached via java client and am trying to put 60 million object into 
memcached. I am using this command to start memcached

memcached -d -vv -m 8000 -l 127.0.0.1 -p 11211 -c 250 -L 2048 -R 100 1000 10 > 
log_ten_seconds

but after putting 20 million objects memcached give me error like 

Failed to write, and not due to blocking: Connection reset by peer
<80 connection closed.
Failed to write, and not due to blocking: Connection reset by peer

Am not sure, where am having problem......I really appreciate if you help me to 
get-out of this hall.

Original comment by umashank...@eco-mail.com on 27 Jul 2012 at 9:26