From a955896fe55f9512902af9643c769570815762d5 Mon Sep 17 00:00:00 2001 From: Danny Auble <da@llnl.gov> Date: Tue, 14 Dec 2010 21:14:01 +0000 Subject: [PATCH] update comments on reservations not being able to handle overlapping jobs in a reservation they shouldn't be able to run in. --- src/plugins/accounting_storage/mysql/as_mysql_rollup.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/plugins/accounting_storage/mysql/as_mysql_rollup.c b/src/plugins/accounting_storage/mysql/as_mysql_rollup.c index 7059e6fc33f..0eaffffe0cd 100644 --- a/src/plugins/accounting_storage/mysql/as_mysql_rollup.c +++ b/src/plugins/accounting_storage/mysql/as_mysql_rollup.c @@ -416,7 +416,10 @@ extern int as_mysql_hourly_rollup(mysql_conn_t *mysql_conn, unless the reservation completely overlaps the other reservation we have no idea how many cpus should be removed since this could be a - heterogeneous system. + heterogeneous system. This same problem exists + when a reservation is created with the ignore_jobs + option which will allow jobs to continue to run in the + reservation that aren't suppose to. */ while((row = mysql_fetch_row(result))) { time_t row_start = slurm_atoul(row[RESV_REQ_START]); -- GitLab