rod.schu...@bull.com writes: > I noticed that the default for max_switch_wait is 300 seconds so I left > the max_time as a time string. I also clarified the documentation.
As far as I can see the max_switch_wait default is 60 seconds.
job_mgr.c:
static uint32_t _max_switch_wait(uint32_t input_wait)
...
static uint32_t max_wait = 60;
What is the reason for having such a short time as the default?
This actually initially made me believe that the --switch option was
broken on our installation. All my test jobs was started and ignored the
--switch requirement. I had not discovered that the default existed yet,
and when I specified "--switch 1" I expected the job to wait until it
could run on a single switch, not simply ignore that option after one
minute. No other job requirements behave this way.
My suggestion is to replace the 60 second default with INFINITE (no
limit) for SLURM 2.4. Then sites who like to limit this use the
max_switch_wait config option.
Regards,
Pär Andersson
NSC
pgpQJ2b0Jqmd8.pgp
Description: PGP signature
