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

Startup order independence #39

Closed
javache opened this issue Mar 16, 2012 · 1 comment
Closed

Startup order independence #39

javache opened this issue Mar 16, 2012 · 1 comment

Comments

@javache
Copy link
Contributor

javache commented Mar 16, 2012

Make the different applications a little bit less dependent from booting in the right order, especially re boxxy and count-von-count.

Idea: keep a state of each Boxxy, whether it is offline or online. If boxxy is offline and a message needs to be sent, first try sending the config to that boxxy. If succesful, mark it as being online. When a boxxy is online and a message fails to be delivered, mark it as offline and restart the procedure.

jaspervdj added a commit that referenced this issue Apr 12, 2012
@jaspervdj
Copy link
Contributor

Not closing because there's still a problem left: one lagging boxxy (e.g., 30s timeout) will result in later boxxies being contacted 30s later. Fix by adding some paralllelism.

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

2 participants