Hello,
Thank you for this explanation.
We also had experienced this problem (when migrating from 16.05.4 to
17.02.1) and fixed it finally by executing database query:
UPDATE slurm_acct_db.prometheus_job_table SET
mem_req=IF(mem_req&0x8000,(mem_req&0x7fff)|0x8000,mem_req);
After some more digging this turns out to be the same issue as in Bug 4153 and
was fixed on September 27th 2017.
If you’ve upgraded to 17.02/17.11 prior to this date, be sure to check your
reqmem data.
> Am 26.01.2018 um 11:59 schrieb Lech Nieroda :
>
> Dear slurm users,
>
> we have run into a
Dear slurm users,
we have run into a problem after upgrading from slurm 15.08.12 to 17.02.6 back
in August 2017: all old jobs which had their memory requested with the
‚mem-per-cpu’ option have shown absurd values in the ‚reqmem‘ attribute when
queried with sacct.
The values were somewhere in t
