From 54091250ae26ad834c46ad8d57b75ecc9ae9c038 Mon Sep 17 00:00:00 2001
From: Moe Jette <jette1@llnl.gov>
Date: Fri, 13 Jun 2008 17:15:01 +0000
Subject: [PATCH] Clarify resource allocation bug
---
NEWS | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/NEWS b/NEWS
index 1c965169674..72156670884 100644
--- a/NEWS
+++ b/NEWS
@@ -14,13 +14,15 @@ documents those changes that are of interest to users and admins.
-- For Moab, sbatch --get-user-env option processed by slurmd daemon
rather than the sbatch command itself to permit faster response
for Moab.
- -- We are not saving a pending job's task distribution, so after restarting
+ -- IMPORTANT FIX: This only effects use of select/cons_res when allocating
+ resources by core or socket, not by nodes or processors (the default).
+ We are not saving a pending job's task distribution, so after restarting
slurmctld, select/cons_res was over-allocating resources based upon an
invalid task distribution value. Since we can't save the value without
changing the state save file format, we'll just set it to the default
- value for now. This may result in a slight variation on how sockets
- and cores are allocated to jobs, but at least resources will not be
- over-allocated.
+ value for now and save it in Slurm v1.4. This may result in a slight
+ variation on how sockets and cores are allocated to jobs, but at least
+ resources will not be over-allocated.
* Changes in SLURM 1.3.3
========================
--
GitLab