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
Error: Server at xyz not available\n at Client.memcachedCommand [as command]
in nodejs with Memcached
#646
Comments
|
Error: Server at xyz not available\n at Client.memcachedCommand [as command]
in nodejs with Memcached in elasticache
Twemproxy conf file memcached: We are not using elasticcache cluster... it is like having a onprem memcached on kubernetes and twemproxy in kubernetes. Yes i am able to connect to memcached hosts. Strange part is after some time, not sure about the time, the error is going away... looks like the server reconnect feature. When i checked the npm module code https://github.com/3rd-Eden/memcached/blob/master/lib/memcached.js Line number: 311,312,313 this the causing the error. Is there anything to do with the server retries or our config is correct and we have set the following in the client poolsize: 70 Please guide us if we are using the correct twem proxy config and client config |
Error: Server at xyz not available\n at Client.memcachedCommand [as command]
in nodejs with Memcached in elasticacheError: Server at xyz not available\n at Client.memcachedCommand [as command]
in nodejs with Memcached
Do you start twemproxy and your application at the same time? Are you sure twemproxy has finished starting up when you connect to it (should finish in a few seconds) Also, what do the logs from twemproxy say (can be enabled with |
getting the error:
Getting data from memCache failed severity:error f.err:{"stack":"Error: Server at xyz not available\n at Client.memcachedCommand [as command] (/service/node_modules/memcached/lib/memcached.js:306:70)\n at Client.get (/service/node_modules/memcached/lib/memcached.js:830:10)\n at /service/repository/data/Repo.js:32:35\n at new Promise ()\n at Repo.get (/service/repository/data/Repo.js:13:16)\n
Client which is connecting is npm memcached
Twemproxy version: 0.5.0
Environemnt: Running twemproxy inside kubernetes
When checked for twemproxy stats no server ejections all the memcached servers are operating normally.
Any lead on how to solve the above error would be really helpful
The text was updated successfully, but these errors were encountered: