[email protected] (Pär Andersson) writes:

> Danny Auble <[email protected]> writes:
>
>> Par, this can probably be fixed in the 2.2 code, but I don't have any
>> time to work on it right now.  Without looking at the code I think the
>> relavant code is in
...
> Our current work-around is to restart slurmctld as needed. I expect the
> problem will go away once we upgrade this cluster from 2.1 to 2.2, as
> the cluster that is already running slurm 2.2 is working fine.

I can confirm that this problem was fixed by upgrading to 2.2. The DBD
and both clusters now run 2.2.4 and updating of default account take
effect immediately on both clusters without having to restart anything.

Regards,
Pär Andersson
NSC

Attachment: pgpqfiZwGY8oi.pgp
Description: PGP signature

Reply via email to