Question & Answer
Question
When estimated runtime is given, job fails with an error message "Bad runtime specification, Job not submitted"
Cause
Maximum CPULIMIT can be different depending on CPUFACTOR specified in lsf.shared
Answer
LSF uses CPUFACTOR specified in lsf.shared file to normalize CPULIMIT across different hardware.
In LSF, users are allowed to provide estimated RUNTIME to better manage resources. However jobs do not have any restrictions on CPULIMIT due to estimated RUNTIME or maximum CPULIMIT.
If for any reason estimated RUNTIME provided via bsub and bmod is more than maximum CPULIMIT (determined using CPUFACTOR), job will not be submitted. Following error will be shown.
'Bad runtime specification. Job not submitted'
Solution: It is recommended to have the correct CPUFACTOR set for processor type in lsf.shared file.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
isg3T1022330