Scheduled task owner takeover
Every scheduled task in Adaxes is owned by a particular Adaxes service instance. Unless the task owner is down, only it will execute that task.
In a multi-server environment, there are two possible outcomes when a task owner stays down for a long time.
- The task is configured to always run on a specific instance – it will not be executed until the owner goes up.
- The task is not configured to always run on a specific instance – another running instance will permanently take over the ownership and run the task.
Ownership takeover does not happen instantly. There is a 2 hour delay to ensure that the owner is actually down and not just temporarily unavailable. In addition, the maximum AD LDS replication interval is taken into account to ensure that the new owner has up-to-date information about the status of the original owner. This interval is 1 hour intrasite and 3 hours intersite.
This means that a service in the same site as the downed owner will decide to seize its tasks after approximately 3 hours of inactivity. If there are no services in the same site as the downed owner, its tasks will be seized by a service from a different site after approximately 5 hours.