No such luck, Aaron. I specified a node count in my original specification. I would have thought what you suggested was the behavior, but it appears not to be.
Thanks, Bill. -- Bill Barth, Ph.D., Director, HPC [email protected] | Phone: (512) 232-7069 Office: ROC 1.435 | Fax: (512) 475-9445 On 5/12/15, 12:36 AM, "Aaron Knister" <[email protected]> wrote: > >I *think* if you specify a node count instead of a specific node range >you'll get what you're looking for. Unless, of course, you're looking to >reserve specific pieces of hardware. > >Sent from my iPhone > >> On May 11, 2015, at 12:27 PM, Bill Barth <[email protected]> wrote: >> >> >> I'm curious what other sites do to keep jobs running in a reservation >>when >> one of the nodes has an error. Obviously if it's an easy fix, then you >> simply fix the node and the reservation can continue to run jobs. Also, >>if >> nodes are available, you may add one to the reservation to make up for >>the >> slack caused by the bad one. One can also make the reservation larger >>by a >> few nodes to account for bad luck. >> >> I'm really wondering if there are any better options or any automated >> options. >> >> What do others do? >> >> Thanks, >> Bill. >> >> -- >> Bill Barth, Ph.D., Director, HPC >> [email protected] | Phone: (512) 232-7069 >> Office: ROC 1.435 | Fax: (512) 475-9445 >> >> >>
