HI, to your first question: I don't know the exact reason, but SchedMD made it pretty clear, that there is a spcific sequence for updates: slurmdbd -> slurmctld -> slurmd -> commands See https://slurm.schedmd.com/SLUG19/Field_Notes_3.pdf (or any of the other field notes) for details. So, I'd advise that you don't try it any other way.
for your second question, see https://slurm.schedmd.com/slurm.conf.html: > MpiParams > MPI parameters. Used to identify ports used by older versions of > OpenMPI and native Cray systems. The input format is > "ports=12000-12999" to identify a range of communication ports to > be used. NOTE: This is not needed for modern versions of OpenMPI, > taking it out can cause a small boost in scheduling performance. > NOTE: This is require for Cray's PMI. Best, Marcus On 20-02-04 11:44, Matthias Krawutschke wrote: > Hello together, > > > > on the RELEASE_NOTES I read the following: > > ---------------------------------------------------------------------------- > -------------------------------- > > Slurm can be upgraded from version 18.08 or 19.05 to version 20.02 without > loss > > of jobs or other state information. Upgrading directly from an earlier > version > > of Slurm will result in loss of state information. > > ---------------------------------------------------------------------------- > -------------------------------- > > > > I want to upgrade or update my ComputeNode first, to see if it work or not, > but this is not able to do. > > I´ve got the message on ComputeNode, that this Node can´t connect to > SLURMCTLD .. > > > > So, why can´t I test the NEW SLURM-Version on Node before I update /upgrade > the Controller and Database? > > It is really important, that I upgrade /update the Database & Controller > first?? > > > > The other point (see my eMail from today) I read on this file too: > > ---------------------------------------------------------------------------- > ------------------------------------- > > CONFIGURATION FILE CHANGES (see man appropriate man page for details) > > ===================================================================== > > -- The mpi/openmpi plugin has been removed as it does nothing. > > MpiDefault=openmpi will be translated to the functionally-equivalent > > MpiDefault=none. > > So, how does OpenMPI and SLURM works together? > > What was the reason, that you disable this function? > > > > > > I hope, you can help me here with my questions . > > > > Best regards . > > > > > > > > Matthias Krawutschke, Dipl. Inf. > > > > Universität Potsdam > ZIM - Zentrum für Informationstechnologie und Medienmanagement > Team High-Performance-Computing > > Campus Am Neuen Palais: Am Neuen Palais 10 | 14469 Potsdam > Tel: +49 331 977-4444, Fax: +49 331 977-1750 > > > > Internet: <https://www.uni-potsdam.de/de/zim/angebote-loesungen/hpc.html> > https://www.uni-potsdam.de/de/zim/angebote-loesungen/hpc.html > > > > > -- Marcus Vincent Boden, M.Sc. Arbeitsgruppe eScience Tel.: +49 (0)551 201-2191 E-Mail: mbo...@gwdg.de --------------------------------------- Gesellschaft fuer wissenschaftliche Datenverarbeitung mbH Goettingen (GWDG) Am Fassberg 11, 37077 Goettingen URL: http://www.gwdg.de E-Mail: g...@gwdg.de Tel.: +49 (0)551 201-1510 Fax: +49 (0)551 201-2150 Geschaeftsfuehrer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Goettingen Registergericht: Goettingen Handelsregister-Nr. B 598 ---------------------------------------
smime.p7s
Description: S/MIME cryptographic signature
