You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1、We use java_memcached-release_2.6.3 as client, and memcached-1.4.13, ibevent 2.0.19-stable as cached sever to cached java object class implements
Serializable.
2、 The problem is after few days or hours, cilent set some newly generated objects to memcached server, result is true, but get null. Then we can only restart memcached server to restore normal work.
3、We have tried to enlarge the memcached server start memory to 6144M, and socket numbers to 30720, result is no help.
./memcached -d -m 6144 -c 30720 -l 127.0.0.1 -p 12000
In addition, we have tried to changed client mode from ASCII to BINARY, also no help.
From the memcached server log , most errors are 'Not found' related, should we upgrade client or server version?
<32 GET TRSGMJC_as_DB7EEF2DE9CB65B4580926F002A5CD74112.125.95.132
And some other results we do not understand while, does symbol of "¬" means error? why some times sending result no length?
<33 get TRSGMJC_ci_customer2D63280F31F7BF796C598B93D6AF5C248.jvm1
33 END
<34 get TRSGMJC_ci_customer2B754127D616479FAC1701D891D348E89.jvm1
34 sending key TRSGMJC_ci_customer2B754127D616479FAC1701D891D348E89.jvm11 0 920
¬
34 END
<34 get TRSGMJC_ls_AFE3D2F7D918D1CCD24A2928723371BA112.125.95.130
34 sending key TRSGMJC_ls_AFE3D2F7D918D1CCD24A2928723371BA112.125.95.130
34 END
<34 get TRSGMJC_ls_AFE3D2F7D918D1CCD24A2928723371BA112.125.95.130
34 sending key TRSGMJC_ls_AFE3D2F7D918D1CCD24A2928723371BA112.125.95.130
34 END
<34 delete TRSGMJC_ci_customer2B754127D616479FAC1701D891D348E89.jvm1
34 DELETED
<34 delete TRSGMJC_ls_AFE3D2F7D918D1CCD24A2928723371BA112.125.95.130
34 DELETED
<34 get TRSGMJC_lu_%E8%B5%B5%E4%B8%96%E5%BA%86
34 sending key TRSGMJC_lu_%E8%B5%B5%E4%B8%96%E5%BA%86
34 END
<34 delete TRSGMJC_lu_%E8%B5%B5%E4%B8%96%E5%BA%86
34 DELETED
<35 get TRSGMJC_ci_customer2A6CB386E832B6503E9AC1DBCB0E6DF14.jvm1
35 END
<32 get TRSGMJC_ci_customer2D2AB156ECC6D893E3F5E917D7FF7EF8E.jvm1
32 END
<33 get TRSGMJC_ci_customer26E78EC90BAAD0F24FC8EE3D1C95F743C.jvm1
33 END
<34 get TRSGMJC_ci_customer2C2FC12CA4544C7C4B73DC98433F6A6AC.jvm1
34 END
<35 get TRSGMJC_ci_customer20AA6067566BF8FDC3A8E514A104AC920.jvm1
35 END
<32 get TRSGMJC_ci_customer2AC9A422BB281E578A37485FF60B3428D.jvm1
32 END
<33 get TRSGMJC_ci_customer288283C65BF3E5D715A80C734DDC490A0.jvm1
33 END
<34 get TRSGMJC_ci_customer2625ECFE1EF83CBB031E1A1048F446FD7.jvm1
34 sending key TRSGMJC_ci_customer2625ECFE1EF83CBB031E1A1048F446FD7.jvm11 0 925
¬
34 END
<34 get TRSGMJC_ls_E8D331B3236FF66BE3225601802C0AFF112.125.95.130
34 sending key TRSGMJC_ls_E8D331B3236FF66BE3225601802C0AFF112.125.95.130 0 925
¬
34 END
<34 get TRSGMJC_ls_E8D331B3236FF66BE3225601802C0AFF112.125.95.130
34 sending key TRSGMJC_ls_E8D331B3236FF66BE3225601802C0AFF112.125.95.130 0 925
¬
34 END
<34 delete TRSGMJC_ci_customer2625ECFE1EF83CBB031E1A1048F446FD7.jvm1
34 DELETED
<34 delete TRSGMJC_ls_E8D331B3236FF66BE3225601802C0AFF112.125.95.130
34 DELETED
<34 get TRSGMJC_lu_%E7%8E%8B%E6%B3%A2111
34 sending key TRSGMJC_lu_%E7%8E%8B%E6%B3%A2111
34 END
<34 delete TRSGMJC_lu_%E7%8E%8B%E6%B3%A2111
34 DELETED
The text was updated successfully, but these errors were encountered:
1、We use java_memcached-release_2.6.3 as client, and memcached-1.4.13, ibevent 2.0.19-stable as cached sever to cached java object class implements
Serializable.
2、 The problem is after few days or hours, cilent set some newly generated objects to memcached server, result is true, but get null. Then we can only restart memcached server to restore normal work.
3、We have tried to enlarge the memcached server start memory to 6144M, and socket numbers to 30720, result is no help.
./memcached -d -m 6144 -c 30720 -l 127.0.0.1 -p 12000
In addition, we have tried to changed client mode from ASCII to BINARY, also no help.
<32 GET TRSGMJC_as_DB7EEF2DE9CB65B4580926F002A5CD74112.125.95.132
<33 get TRSGMJC_ci_customer2D63280F31F7BF796C598B93D6AF5C248.jvm1
The text was updated successfully, but these errors were encountered: