Details
-
Improvement
-
Resolution: Won't Fix
-
Minor
-
None
-
3.0.1
-
None
-
Security Level: Public
-
None
Description
This error message is very confusing.
Temporary error is very vague and may mean that server is overloaded or out of memory or God knows what.
Please change the message (but keep the code) in case client just locked the key with GETL operation.
Now we get this obscure output:
No. Time Source Destination Protocol Expert Info Len srcport
|
214162 2015-07-23 19:38:29.650829000 cust4sdf1db11 cust4rtc3 MEMCACHE Note Append Response (Unknown status: 134) 109 11210
|
|
Frame 214162: 109 bytes on wire (872 bits), 109 bytes captured (872 bits) on interface 0
|
Linux cooked capture
|
Internet Protocol Version 4, Src: cust4sdf1db11 (10.112.68.7), Dst: cust4rtc3 (10.112.68.42)
|
Transmission Control Protocol, Src Port: 11210 (11210), Dst Port: 53379 (53379), Seq: 1060019, Ack: 548139, Len: 41
|
Memcache Protocol, Append Response
|
Magic: Response (129)
|
Opcode: Append (14)
|
Key Length: 0
|
Extras length: 0
|
Data type: Raw bytes (0)
|
Status: Unknown (134)
|
[Value length: 17]
|
Total body length: 17
|
Opaque: 0
|
CAS: 0
|
Value: Temporary failure
|
We suggest to keep
Status: Unknown (134) <<< ENGINE_TMPFAIL
but change this from
Value: Temporary failure
to
Value: Lock error
Attachments
Issue Links
- relates to
-
-
- Closed
-