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

Job stuck in "active" state #31

Open
colaskirschoff opened this issue Aug 27, 2018 · 3 comments
Open

Job stuck in "active" state #31

colaskirschoff opened this issue Aug 27, 2018 · 3 comments

Comments

@colaskirschoff
Copy link

I have a queue of jobs that is started in background whenever there is connexion. It's been three days that one job is stuck in the queue, while more recent jobs were processed without any issue.

{
"0": {
"id": "34c7d35c-8c43-48f3-ac17-880029a7d747",
"name": "place-association",
"payload": "{"stopId":"576e78b9-fa5b-472f-89e9-5c1e3ace7d7b"}",
"data": "{"attempts":1}",
"priority": 10,
"active": true,
"timeout": 5000,
"created": "2018-08-24T19:38:21.128Z",
"failed": null
}
}

For now I set active to false to start it back. Any idea of what's happening ? Thx :)

@lyseiha
Copy link

lyseiha commented Dec 5, 2018

I have the same problem. It happens whenever i stop queue from processing.

@rheilgm
Copy link

rheilgm commented Dec 6, 2018

const initialQuery = (queueLifespanRemaining) ? 'active == FALSE AND failed == null AND timeout > 0 AND timeout < ' + timeoutUpperBound : 'active == FALSE AND failed == null';

yeah it only process queue that are not active and will skip those active ones i wonder if changing this query to something like:

const initialQuery = (queueLifespanRemaining) ? 'failed == null AND timeout > 0 AND timeout < ' + timeoutUpperBound : 'failed == null';
so that it will process queue as long as it wont hit the retry count?
because there are cases like app was forcefully closed and it is already set to active then boom we cant run that job again

@famousfilm
Copy link

This sounds similar to #24 . @billmalarky explains what's going on there and I posted a rough work-around.

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

4 participants