i've been getting random bursts of many errors from memjs with "socket timed out waiting on response".
- remote memcached server
- keepAlive enabled
- timeout set 2s
additionally, i am dealing with objects that are usually small, but sometimes up to 6MB.
after looking through the memjs code, i think this is user error on my part since i'm guessing it's taking longer than 2s to receive the complete response for a get op in some situations.
in my case, i'll probably set the timeout to something very high like 60s, since i primarily use just get/set. but that won't be ideal if an incr/decr/delete/etc takes a minute to fail.
a doc change might be nice though. my reading of timeout dumbly assumed it was time until the server acknowledged/started processing an operation, and not the end-to-end total operation timeout. maybe mentioning that the default timeout may not be appropriate depending on object size and network servers or whatever.
i've been getting random bursts of many errors from memjs with "socket timed out waiting on response".
additionally, i am dealing with objects that are usually small, but sometimes up to 6MB.
after looking through the memjs code, i think this is user error on my part since i'm guessing it's taking longer than 2s to receive the complete response for a get op in some situations.
in my case, i'll probably set the timeout to something very high like 60s, since i primarily use just get/set. but that won't be ideal if an incr/decr/delete/etc takes a minute to fail.
a doc change might be nice though. my reading of timeout dumbly assumed it was time until the server acknowledged/started processing an operation, and not the end-to-end total operation timeout. maybe mentioning that the default timeout may not be appropriate depending on object size and network servers or whatever.