The reservations in the database are only for historical purposes, they
don't get read in from the slurmctld. The DBD should be purging them as
configured you shouldn't have the manually do anything.
On 07/07/15 14:35, Bill Barth wrote:
On 7/7/15, 7:31 AM, "John Desantis" <[email protected]> wrote:
Are you using SlurmDBD or the MySQL accounting plugin? Since you've
re-created all reservations and there is still unintentional
overlapping occurring, I'd recommend looking at the reservation
table(s) within the DB and possibly truncating it(them).
We are just in order to get fairshare. I'm not gonna do that in production
though, that sounds dangerous.
Thanks,
Bill.
