Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Slurm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tud-zih-energy
Slurm
Commits
699b38d9
Commit
699b38d9
authored
15 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
Update RELEASE_NOTES for recent updates
parent
cefecdc8
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
RELEASE_NOTES
+21
-15
21 additions, 15 deletions
RELEASE_NOTES
with
21 additions
and
15 deletions
RELEASE_NOTES
+
21
−
15
View file @
699b38d9
RELEASE NOTES FOR SLURM VERSION 2.2
05
Jan
uary 2010 (through SLURM 2.
1
.0)
05
Febr
uary 2010 (through SLURM 2.
2
.0
-pre1+
)
IMPORTANT NOTE:
SLURM state files in version 2.2 are different from those of version 2.1.
After installing SLURM version 2.2, plan to restart without preserving
jobs or other state information. While SLURM version 2.1 is still running,
cancel all pending and running jobs (e.g.
"scancel --state=pending; scancel --state=running"). Then stop and restart
daemons with the "-c" option or use "/etc/init.d/slurm startclean".
If using the slurmdbd (SLURM DataBase Daemon) you must update this first.
The 2.2 slurmdbd will work with SLURM daemons at version 1.3.0 and above.
You will not need to update all clusters at the same time, but it is very
...
...
@@ -18,12 +11,12 @@ any other clusters making use of it. No real harm will come from updating
your systems before the slurmdbd, but they will not talk to each other
until you do.
There are substantial changes in the slurm.conf configuration file. It
is recommended that you rebuild your configuration file using the tool
doc/html/configurator.html that comes with the distribution.
SLURM can be upgraded from version 2.1 to version 2.2 without loss of jobs or
other state.
HIGHLIGHTS
==========
* Slurmctld restart/reconfiguration operations have been altered.
NOTE: There will be no change in behavior unless partition configuration
or node Features/Weight are altered using the scontrol command to differ
...
...
@@ -47,15 +40,31 @@ HIGHLIGHTS
was formerly always recreated from slurm.conf.
CONFIGURATION FILE CHANGES (see "man slurm.conf" for details)
=============================================================
* Added VSizeFactor to enforce virtual memory limits for jobs and job steps as
a percentage of their real memory allocation.
COMMAND CHANGES (see man pages for details)
===========================================
* sinfo -R now has the user and timestamp in separate fields from the reason.
BLUEGENE SPECIFIC CHANGES
=========================
OTHER CHANGES
=============
* Much functionality has been added to account_storage/pgsql. The plugin
is still in a very beta state.
* SLURM's PMI library (for MPICH2) has been modified to properly execute an
executable program stand-alone (single MPI task launched without srun).
* Added support for spank_get_item() to get S_STEP_ALLOC_CORES and
S_STEP_ALLOC_MEM. Support will remain for S_JOB_ALLOC_CORES and
S_JOB_ALLOC_MEM.
API CHANGES
===========
* Changed members of the following structs:
job_info_t
num_procs -> num_cpus
...
...
@@ -85,6 +94,3 @@ update_node_msg_t
* Added the following API's
* Changed the following API's
OTHER CHANGES
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment