From fc62fc984bdbb5e1a7966a6aef6981809ad303b8 Mon Sep 17 00:00:00 2001
From: Danny Auble <da@schedmd.com>
Date: Tue, 30 Jan 2018 11:46:19 -0700
Subject: [PATCH] Better explaination (hopefully) of how to avoid waiting for
the db_index when sending a start message to the database.
Bug 4502
---
.../slurmdbd/accounting_storage_slurmdbd.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/plugins/accounting_storage/slurmdbd/accounting_storage_slurmdbd.c b/src/plugins/accounting_storage/slurmdbd/accounting_storage_slurmdbd.c
index 430ab94becf..4734682300f 100644
--- a/src/plugins/accounting_storage/slurmdbd/accounting_storage_slurmdbd.c
+++ b/src/plugins/accounting_storage/slurmdbd/accounting_storage_slurmdbd.c
@@ -2551,10 +2551,11 @@ extern int jobacct_storage_p_job_start(void *db_conn,
msg.msg_type = DBD_JOB_START;
msg.data = &req;
- /* if we already have the db_index don't wait around for it
- * again just send the message. This also applies when the
- * slurmdbd is down and we are about to remove the job from
- * the system.
+ /* If we already have the db_index don't wait around for it
+ * again just send the message when not resizing. This also applies
+ * when the slurmdbd is down and we are about to remove the job from
+ * the system. We don't want to wait for the db_index in that situation
+ * either.
*/
if ((req.db_index && !IS_JOB_RESIZING(job_ptr))
|| (!req.db_index && IS_JOB_FINISHED(job_ptr))) {
--
GitLab