How To
Summary
Sometimes MaxSlot information is inconsistent on different pages. For example, the "Cluster > Job info > By host" page shows that the test01 host has 16 slots as MaxSlot. But the "Cluster > Host info > Servers" page shows that test01's MaxSlot is 8.
Steps
RTM collected information via LSF. The inconsistency comes from the difference between "lshosts" and "bhosts".
The MaxSlot on the page of "Cluster" > "JobInfo" > "ByHost" is the number of job slots on the host. It is configurable at LSF side by modifying the $LSF_ENVDIR/lsbatch/<clustername>/configdir/lsb.hosts. The information displayed on this page follows the "bhosts" output.
The MaxSlot on the page of "Cluster" > "HostInfo" > "Servers" is the default number of job slots on the host. It is not configurable at LSF side. The information is collected by LIM daemon. You can check it by "lim -t" on the local host. The information displayed on this page follows the "lshosts" output.
- The "lshosts" output is static, usually not configurable. The "bhosts" output is dynamic, usually configurable.
- On the "Cluster" > "HostInfo "> "Servers" page, there is a short explanation under "MaxSlot" column shown as "Default maximum scheduling slots".
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
30 November 2020
UID
ibm16370549