AutoSys load balancing does not seem to be working.

Document ID : KB000011072
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

A machine is defined with a max_load of 100 yet multiple jobs are allowed to start on that machine which push the current load above its max_load as defined in its machine definition.

 

Example:

[autosys@host1]$ autorep -q -M host1

 

/* ----------------- host1 ----------------- */

 

insert_machine: host1

type: r

max_load: 100

factor: 1.00

 

[autosys@host1]$ autorep -q -J job%

 

/* ----------------- job1 ----------------- */

 

insert_job: job1   job_type: c

command: sleep 60

machine: host1

owner: autosys@host1

permission: gx,ge,wx,we

alarm_if_fail: 1

job_load: 100

 

/* ----------------- job2 ----------------- */

 

insert_job: job2   job_type: c

command: sleep 60

machine: host1

owner: autosys@host1

permission: gx,ge,wx,we

alarm_if_fail: 1

job_load: 100

 

[autosys@host1]$ sendevent -E STARTJOB -J job1

[autosys@host1]$ sendevent -E STARTJOB -J job2

 

[autosys@host1]$ autorep -M host1

 

Machine Name    Max Load  Current Load  Factor   O/S       Status

______________ __________ ____________ _______ ___________ ______

host1              100       200        1.00     Unix      Online

 

Environment:
Product: Workload Automation AE 11.xPlatform: Windows, UNIX, LinuxDatabase: Oracle, Sybase, MS SQL
Answer:

The job attributes "job_load" and "priority" are required for Autosys to take into consideration the max and/or current load of a machine. In the above example the priority field is missing, as a result both jobs are allowed to start. If they both included "priority", job1 would start and job2 would go into QU (Queue wait) until job1 completes. Then job2 would be allowed to run.