Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sporadic bursts of error: socket timed out waiting on response #171

Open
cmawhorter opened this issue Jun 15, 2023 · 0 comments
Open

Sporadic bursts of error: socket timed out waiting on response #171

cmawhorter opened this issue Jun 15, 2023 · 0 comments

Comments

@cmawhorter
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant