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.

Sign up for GitHub

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

Jump to bottom

QueueTerminated/NoMoreWork messages can lose Work (potentially) #84

Closed
nsauro opened this issue Jul 5, 2016 · 1 comment
Closed

QueueTerminated/NoMoreWork messages can lose Work (potentially) #84

nsauro opened this issue Jul 5, 2016 · 1 comment
Assignees
@nsauro
Labels
bug discussion needed in progress scope:medium

Comments

@nsauro
Copy link
Contributor

nsauro commented Jul 5, 2016

Just tracking this:

Right now in the waitingForRoutee state, if there is Work queued, and the Worker receives a Terminated(queue) or a NoWorkLeft message, it will stop itself, and not execute the Work.

This also is a non issue, if we do away with this waitingForRoutee state.
@nsauro nsauro changed the title Potential Work loss QueueTerminated/NoMoreWork messages can lose Work (potentially) Jul 5, 2016
@nsauro
Copy link
Contributor Author

nsauro commented Jul 13, 2016

Working on this by way of #92

@nsauro nsauro self-assigned this Jul 13, 2016
@nsauro nsauro mentioned this issue Jul 13, 2016
Merged
@nsauro nsauro closed this as completed Jul 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nsauro nsauro

Labels
bug discussion needed in progress scope:medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nsauro