Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

timeout but failed to retry until restarting program

See original GitHub issue

Hi, I am using memjs 1.2.0 with memcache. However it sometimes go into fail state for every request until I restart program:

error: socket timed out connecting to server.
 at Socket.<anonymous> (/path/node_modules/memjs/lib/memjs/server.js:169:20)
 at Object.onceWrapper (events.js:272:13)
 at Socket.emit (events.js:180:13)
 at Socket.emit (domain.js:421:20)
 at Socket._onTimeout (net.js:396:8)
 at ontimeout (timers.js:466:11)
 at tryOnTimeout (timers.js:304:5)
 at Timer.listOnTimeout (timers.js:267:5)

Node v9.9.0

Issue Analytics

State:
Created 5 years ago
Reactions:5
Comments:28 (12 by maintainers)

Top GitHub Comments

2reactions

saschatcommented, Oct 25, 2019

@UmanShahzad any help is appreciated. I have been unable to reproduce this issue so also a pointer on how to reproduce this error would help a lot.

1reaction

saschatcommented, Sep 24, 2020

@tengattack I finally understand what you mean 😃

This would be an option (we actually use event emitters internally) but I don’t think this would be ideal since it would remove choice for the user. For example lets consider a get request. It can return a hit, a miss, or an error. If I use an event emitter for errors a get only returns a hit or a miss. This means as a library developer I need to decide for you how to treat this error. Now in a get request this might be easy (I would treat it as a miss), but what about a set or an incr command.

So to summarize, an event emitter would basically mean that as the library developer I would have to decide how to treat all errors for the different commands and as a user you only get to react to errors in one way, independently which command they occurred with. The second might not be too mad but the former I am not comfortable doing.

Top Results From Across the Web

IIS fails to restart with a timeout error - Stack Overflow

We restart IIS by going into the IIS manager, clicking on the server name, and then clicking Restart on the right. The system...

Troubleshoot Lambda function retry and timeout issues ... - AWS

To troubleshoot the retry and timeout issues, first review the logs of the API call to find the problem. Then, change the retry...

Windows Autopilot known issues - Microsoft Learn

The current workaround for this issue is to restart the ODJConnectSvc.exe service. Reset button causes pre-provisioning to fail on retry. When ...

Retry-ability - Cypress Documentation

What you'll learn How Cypress retries commands and assertions When ... still fails, Cypress continues retrying until the cy.find() timeout is reached.

Queues - Laravel - The PHP Framework For Web Artisans

Cleaning Up After Failed Jobs; Retrying Failed Jobs ... Laravel queues provide a unified queueing API across a variety of different queue backends, ......