-
Notifications
You must be signed in to change notification settings - Fork 14
SchedulerRedundancy
Since a job scheduler only queues work, but does not process it there is no performance benefit to having multiple schedulers with the same schedules.
However, you may wish to have have multiple schedulers for redundancy. This is possible, but a little tricky. In order for this to work correctly, the system time clocks on each machine must be in sync. Ideally, they should have less than 1 second of difference.
In order for the time windows to be calculated correctly by the consumers, there clocks should be in sync as well.
There are a couple of options:
-
Ensure that all machines running scheduler or consumer instances have in-sync clocks.
-
Use a common time provider for all schedulers and consumers. The same instance isn't required, but they should all be the same type.
See Time Settings for details on injecting time providers
For any issues please use the GitHub issues