Skip to content
This repository has been archived by the owner on Nov 2, 2021. It is now read-only.

Fix out of order execution on remote nodes #6

Open
magnusfeuer opened this issue Dec 2, 2014 · 0 comments
Open

Fix out of order execution on remote nodes #6

magnusfeuer opened this issue Dec 2, 2014 · 0 comments

Comments

@magnusfeuer
Copy link
Member

If two different services are invoked on a remote node that is currently not available, the services may be invoked out of order when the node does become connected. Scheduluer should queue messages on a per-node basis, not per-service.

magnusfeuer added a commit that referenced this issue Aug 17, 2015
added svc reg+call tests + bug fixes
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant