Differences in LSF Configuration between Juno and luna
- We reserve ~12GB of RAM per host for the operating system and GPFS on Juno CentOS 7 hosts.
- On each jx## node (CentOS 7, GPFS installed), 240GB of RAM is available for LSF jobs.
- When specifying RAM for LSF jobs, specify GB of RAM per task (slot) on Juno (unlike luna, where RAM is specified per job).
- All jobs must have -W (maximum execution Walltime) specified on Juno. Please do not use -We on Juno.
- There is no /swap on CentOS 7 nodes. Memory usage is enforced by cgroups so jobs never swap. A job will be terminated if memory usage exceeds its LSF specification.
- All Juno compute hosts have access to internet.
- To check jobs which are DONE or status EXIT, use "bhist -l JobID" or "bhist -n 0 -l JobID". bacct is also available. "bjobs -l JobID" only shows RUNNING and PEND jobs.
- The maximum hold time for DONE/EXIT jobs information is 24 hours in bjobs command.
Example: bsub -w "post_done('JOB_A') -J "JOB_B" ... if JOB_A DONE 24 hours earlier then JOB_B was submitted, JOB_B won't start - There is no iounits resource on Juno.
- CMOPI SLA configured on Juno. The loan policies are: 100% resources for 90 mints jobs for not SLA users, and 50% resources for 360 mints jobs for not SLA users.
- The rest SLAs. The loan policy is: 100% resources for 360 mints jobs for not SLA users