[slurm-users] Fairshare tree after SLURM upgrade

[Lech Nieroda]

Also keep in mind that the default FairTree Algorithm changes in 19.05 to FAIR_TREE. You’d have to set the PriorityFlag to NO_FAIR_TREE in order to revert to the classic algorithm, otherwise your FairShare calculations will be quite different even though the raw usage data remains the same.

Kind regards,
Lech

> Am 29.01.2021 um 08:44 schrieb Ole Holm Nielsen <Ole.H.Nielsen at fysik.dtu.dk>:
> 
> On 1/29/21 8:03 AM, Gestió Servidors wrote:
>> I’m going to upgrade my SLURM version from 17.11.5 to 19.05.1. I know this is not the last version, but I manage another cluster that is running, also, this version. My question is: during the process, I need to upgrade “slurmdbd”. All the fairshare tree (with rawusage, effectvusage, fairshare, etc), will be kept in the new version after upgrading?
> 
> Beware: You can as a maximum upgrade only by 2 Slurm major versions!
> This is well known, see a summary in https://wiki.fysik.dtu.dk/niflheim/Slurm_installation#upgrading-slurm
> 
> All data in your database will be migrated correctly to the new Slurm version.  This assumes that your upgrade process worked without errors! Older MySQL versions may have problems!
> 
> Therefore it is critical to first test the database upgrade on a test system!  Please see the above page for advice on the upgrade testing.
> 
> /Ole
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5221 bytes
Desc: not available
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20210129/f9c0c15d/attachment-0001.bin>