Current Architecture
Architecture: Supervisor and Master / Universal Agent Cluster
Master Cluster
- Master Cluster members use the same database
- Instances operate either in active-passive mode or in active-active mode
- Cluster members in active-active mode share the workload of local jobs
- Cluster members can use Agents to execute jobs on remote servers
Universal Agent Cluster
- Each Agent is addressed by a Master configuration
- A number of Agents is grouped in a Cluster for:
- fixed priority scheduling
- round-robin scheduling
Job Execution
- Jobs are executed locally per JobScheduler Master
- Jobs are executed locally per JobScheduler Agent
- No central resources required for job execution
Benefits of the current Architecture