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

Timedout Queues #85

Open
ahaverty opened this issue Oct 16, 2016 · 3 comments
Open

Timedout Queues #85

ahaverty opened this issue Oct 16, 2016 · 3 comments

Comments

@ahaverty
Copy link

Setting numWorkers to 100, and running tasks until they timeout, appears to be not releasing queues. I haven't isolated code to prove yet, but I wanted to ask for more detail about how timeouts are intended to be used.

Is the above by design, should I be manually timing out my tasks and resolving like the guide example does, or is this a bug?

@ahaverty
Copy link
Author

For example, the first 100 tasks appear to be taken and timedout, but nothing after that first 100 is picked up by a queue

@cbraynor
Copy link
Contributor

cbraynor commented Nov 4, 2016

100 workers is a large number of tasks to be processed in parallel in a single node process for most tasks (unless they're highly async). First off, I'd suggest lowering the number of workers per process, and try running multiple node processes, or spawning child processes to do the processing.

Let me know if you still have issues after trying that - you might simply be trying to do too much on a single CPU

@cbraynor
Copy link
Contributor

the 1.6.1 release fixed a bug in timeouts that could be related to some of these symptoms. Can you check out the new release and report back if things still don't work as you expect

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

2 participants