You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2022. It is now read-only.
Need to write a simple cluster mode for the scheduler to ensure that only one scheduler is ever in control in cluster mode, could be an interesting excercise re. NodeJS support for multi-cast among members of a cluster or a use of socket.io perhaps?
The text was updated successfully, but these errors were encountered:
The scheduler runs effectively as a background task that is started as soon as the app is, when you run it in cluster mode (node app-cluster), it runs 4 servers - hence, you get four schedulers. This means any job you have configured runs 4 times. We need to change it so that when a scheduler starts, it checks if any other schedulers are running on other nodes (you do this via multicast or by holding a specific port on the server open) and if so, going to sleep.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Need to write a simple cluster mode for the scheduler to ensure that only one scheduler is ever in control in cluster mode, could be an interesting excercise re. NodeJS support for multi-cast among members of a cluster or a use of socket.io perhaps?
The text was updated successfully, but these errors were encountered: