I'm working on getting a test going internally. I'll let you know how it
goes.
*Scott Mansfield*
Product Eng > Consumer Science Eng > Sr. Software Eng
{
M: 352-514-9452
E: smansfi...@netflix.com
K: {M: mobile, E: email, K: key}
}
On Mon, Sep 7, 2015 at 2:33 PM, dormando wrote:
> Yo,
>
>
Hi, We recently encountered an issue in prod. There were two memcache
servers used. One of it went to hung state (not completely down).
Do we have any way to identify the bad node when exception happens?
--
---
You received this message because you are subscribed to the Google Groups
"mem
hi,
what memcached version do you use?
what is "hung state"?
can you use "echo stats | nc 11211?
what do you mean by "exception" ("when exception happens")? (memcached does
not throw exceptions)
On Wednesday, September 9, 2015 at 1:49:53 PM UTC-7, mail...@gmail.com
wrote:
>
> Hi, We recentl
store four key-value pairs:
id->full struct
key1->id
key2->id
key3->id
i hope keys(key1..3 are uniq)
so, storing will be one op with four values and retrieving will be two ops
get key and than get id
i still think i miss something because of this phrase "I guess no because
duplicate keys are o
Thanks for the reply.
keys 1..3 are unique for id, means for several requests generated by
particular id. BTW in *key1->id, *by id you mean value of key. right?
What I meant by that phrase is that if i store *id:value* once and again
for next request by same or diff id I'll have to add again *
