AutoSys tie-breaker scheduler situtations

Products

• Autosys Workload Automation

Issue/Introduction

AutoSys has a tie-breaker scheduler available. The documentation suggest it is need only if the configuration includes dual databases and dual schedulers.

 

Resolution

A tie-breaker scheduler is only needed if the configuration includes BOTH dual schedulers and dual databases. In the situation where the configuration includes only one database there is no need for a tie-breaker scheduler as any other schedulers would only be trying to communicate with that one db.  So there is no confusion as to which scheduler is in control. If the configuration includes two databases then there could be the possibility where the primary scheduler loses connection to DB#2 but is still communicating to DB#1 meanwhile the shadow is communicating with DB#2 but not DB#1.  So both schedulers might think or want to be in control, hence the need for the tie-breaker.  The shadow scheduler would only take over if it sees the primary has gone stale and the tie-breaker scheduler is still active in the database that the shadow is connected to.

The schedulers update the ujo_ha_process table in the database(s) with their host's current timestamp.  This allows other know it is still active.