Make sure the FUTURE node is not included in any partition.
On Fri, Jul 14, 2017 at 5:27 PM, Robbert Eggermont <[email protected]> wrote: > > Hello, > > We're adding some nodes to our cluster (17.02.5). In preparation, we've > defined the nodes in our slurm.conf with "State=FUTURE" (as descibed in the > man page). But it doesn't work like this, because when we start the slurmd > on the nodes, the nodes immediately show up as idle. > > When we manually run "scontrol update NodeName=XXX State=FUTURE" the node > becomes invisible, as expected for State=FUTURE. However, after a restart > of the node (or the slurmd), the node is in state idle again, and jobs get > scheduled on the node... > > So, how do we make the nodes go into State=FUTURE automatically? > Or do we simply remove the node definitions until the nodes are ready? > > Robbert > > -- > Robbert Eggermont Intelligent Systems > [email protected] Electr.Eng., Mathematics & Comp.Science > +31 15 27 83234 Delft University of Technology >
