Looks ok to me. Maybe add step 2.5 shut down any nodes pointing to the old slurmdbd, and step 3.5 shut down the old slurmctld and slurmdbd.
Obviously if you're changing slurmctld and/or slurmdbd hostnames, then update the client configs. Paddy On Wed, Jan 04, 2017 at 07:44:39AM -0800, Riccardo Murri wrote: > > Hello, > > my site is performing an upgrade of SLURM from version 14.11 to 15.08. > To (possibly) further complicate the matter, we are running a new set > of service nodes (SLURM controller, DB host) for the new SLURM. What > is the recommended procedure to upgrade yet keep the DB accounting > records available? Would the following work? > > 1. Shut off the new (15.08) slurmctld and slurmdbd > 2. Drop the new accounting DB (to make sure we start clean) > 3. Clone the old acct DB into the new location: mysqldump ... | mysql > 4. Start the new slurmdbd > 5. Wait for some signal in the logs that migration is finished? > 6. Start the new slurmctld > > Thanks, > Riccardo > > -- > Riccardo Murri > http://www.s3it.uzh.ch/about/team/#Riccardo.Murri > > S3IT: Services and Support for Science IT > University of Zurich > Winterthurerstrasse 190, CH-8057 Zürich (Switzerland) > Tel: +41 44 635 4208 > Fax: +41 44 635 6888 -- Paddy Doyle Trinity Centre for High Performance Computing, Lloyd Building, Trinity College Dublin, Dublin 2, Ireland. Phone: +353-1-896-3725 http://www.tchpc.tcd.ie/
