Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: library
-
Security Level: Public
-
Labels:
-
Environment:libmemcached 1.0.2 and pecl memached 2.x
EC2, PHP
Couchbase Server 1.8.0, single node (test) or several nodes (seen in production)
Description
A load generator test shows the client getting NOT FOUND errors when getting values that have just been set. A manual check shows the values are there.
If the server or moxi is overloaded, or there are too many connections on the host, it should return a timeout, connection error, server down, etc. But not a NOT FOUND error, which prevents the client from dealing properly with the underlying error.
Also, moxi should provide some message in its error logs if there is a connection problem.
With the test case scenario, this NOT FOUND error went away when switching to persistent connections in the new Memcached() call. So it seems some other (connection-related) error is being converted to NOT FOUND incorrectly.
If the server or moxi is overloaded, or there are too many connections on the host, it should return a timeout, connection error, server down, etc. But not a NOT FOUND error, which prevents the client from dealing properly with the underlying error.
Also, moxi should provide some message in its error logs if there is a connection problem.
With the test case scenario, this NOT FOUND error went away when switching to persistent connections in the new Memcached() call. So it seems some other (connection-related) error is being converted to NOT FOUND incorrectly.
Test run in EC2, single-node Couchbase 1.8 cluster, test app running on the same node connecting to localhost:11211.