Plan-based allocation
Plan-based scheduling and reservations requires an allocation plan.
Viewing the allocation plan
Whenever the allocation plan is updated, the planner process dumps a snapshot of the allocation plan in JSON format to the LSF working directory, located at $LSF_ENVDIR/../work/<clustername>/logdir/lsb.allocation.plan.json.
For example, the allocation plan with plans for two jobs would appear like the following:
> cat $LSF_ENVDIR/../work/montreal/logdir/lsb.allocation.plan.json
{
"TIMESTAMP":"Mar 29 15:07:50 2018",
"CHILD_PID":"18939",
"NUM_PLANS":"2",
"PLANS":[
{
"JOB_ID":"montreal@172024",
"RANK":"1",
"START_TIME":"1522351070",
"START_TIME_H":"Mar 29 15:17:50 2018",
"FINISH_TIME":"1522351670",
"FINISH_TIME_H":"Mar 29 15:27:50 2018",
"ALLOC":[
{
"HOST":"host0",
"RSRC":[
{
"NAME":"slots",
"AMOUNT":23
}
]
}
]
},
{
"JOB_ID":"montreal@172025",
"RANK":"2",
"START_TIME":"1522351752",
"START_TIME_H":"Mar 29 15:29:12 2018",
"FINISH_TIME":"1522352352",
"FINISH_TIME_H":"Mar 29 15:39:12 2018",
"ALLOC":[
{
"HOST":"host0",
"RSRC":[
{
"NAME":"slots",
"AMOUNT":23
}
]
}
]
}
]
}
Viewing the allocation plan for a job
Users can view the allocation plan for individual jobs using the bjobs command with the –plan option. Use bjobs –plan to display PEND jobs with allocation plans.
The bjobs –l command also displays allocation plan:
- bjobs –l : display the planned start time for all jobs with a plan.
- bjobs –l –plan : filter for jobs with plans, displaying the planned start time and planned allocation for each job.
Example: Filtering for jobs with a plan:
username1@intel4-74: bjobs -plan
JOBID USER STAT QUEUE FROM_HOST EXEC_HOST JOB_NAME SUBMIT_TIME
172024 username1 PEND normal intel4 x Mar 29 15:07
172025 username1 PEND normal intel4 x Mar 29 15:07
Example: Viewing the planned start time for a job:
username1@intel4-71: bjobs -l 172024
Job <172024>, User <uesrname1>, Project <default>, Status <PEND>, Queue <normal>
, Job Priority <500>, Command <x>
Thu Mar 29 15:07:26: Submitted from host <intel4>, CWD <$HOME>, 23 Task(s), Spe
cified Hosts <host0>;
ESTIMATED_RUNTIME
10.0 min of intel4 based on user provided runtime estimation.
PENDING REASONS:
Not enough processors to meet the job's spanning requirement: 1 host;
Not specified in job submission: 4607 hosts;
Closed by LSF administrator: 1 host;
SCHEDULING PARAMETERS:
r15s r1m r15m ut pg io ls it tmp swp mem
loadSched - - - - - - - - - - -
loadStop - - - - - - - - - - -
RESOURCE REQUIREMENT DETAILS:
Combined: select[type == any] order[r15s:pg]
Effective: -
PLANNED ALLOCATION:
Rank: 1
Start Time: Mar 29 15:21:42 2018
Finish Time: Mar 29 15:31:42 2018
Example: Viewing the planned start time and planned allocation for a job:
username1@intel4-73: bjobs -l -plan 172024
Job <172024>, User <username1>, Project <default>, Status <PEND>, Queue <normal>
, Job Priority <500>, Command <x>
Thu Mar 29 15:07:26: Submitted from host <intel4>, CWD <$HOME>, 23 Task(s), Spe
cified Hosts <host0>;
ESTIMATED_RUNTIME
10.0 min of intel4 based on user provided runtime estimation.
PENDING REASONS:
Not enough processors to meet the job's spanning requirement: 1 host;
Not specified in job submission: 4607 hosts;
Closed by LSF administrator: 1 host;
SCHEDULING PARAMETERS:
r15s r1m r15m ut pg io ls it tmp swp mem
loadSched - - - - - - - - - - -
loadStop - - - - - - - - - - -
RESOURCE REQUIREMENT DETAILS:
Combined: select[type == any] order[r15s:pg]
Effective: -
PLANNED ALLOCATION:
Rank: 1
Start Time: Mar 29 15:22:15 2018
Finish Time: Mar 29 15:32:15 2018
Resources:
host0
slots: 23