Re: [slurm-users] [Long] Why are tasks started on a 30 second clock?

2019-07-26 Thread Kirill Katsnelson
On Thu, Jul 25, 2019 at 10:20 PM Benjamin Redling < benjamin.ra...@uni-jena.de> wrote: > If the 30s delay is only for jobs after the first full queue than it is > backfill in action? > I'm certain this is not the backfill. I see the same behavior when I boot the controller with all nodes in idle+

Re: [slurm-users] [Long] Why are tasks started on a 30 second clock?

2019-07-25 Thread Kirill Katsnelson
On Thu, Jul 25, 2019 at 8:16 AM Mark Hahn wrote: > how about a timeout from elsewhere? for instance, when I see a 30s delay, > I normally at least check DNS, which can introduce such quantized delays. > Thanks, it's a good guess, but is very unlikely the case. The Google Cloud is quite differe

[slurm-users] [Long] Why are tasks started on a 30 second clock?

2019-07-25 Thread Kirill Katsnelson
I am setting up and debugging a little (up to 100 nodes) elastic cluster in the Google Compute Engine (GCE). Our compute load is embarrassingly parallelizable, and I am just packing nodes with a either a task per core for CPU, or task per node for GPU loads, and the node VMs are started and deleted