Hi,
We're using
/opt/slurm/bin/scontrol version
slurm 2.1.14
we have qos=normal,high and bump available
antonmaster3:~$ sacctmgr list qos
Name Priority Preempt GrpJobs GrpNodes GrpSubmit MaxJobs
MaxNodes MaxSubmit MaxWall
---------- ---------- ---------- ------- -------- --------- -------
-------- --------- -----------
normal 0
high 100
bump 1000
low 0
antonmaster3:~$ sacctmgr list clusters
Cluster ControlHost ControlPort RPC FairShare GrpJobs GrpNodes
GrpSubmit MaxJobs MaxNodes MaxSubmit MaxWall QOS
---------- --------------- ------------ --- --------- ------- --------
--------- ------- -------- --------- ----------- --------------------
antons 127.0.0.1 6817 7 0
high,normal
but I can't get qos reported with sacct. It claims UNKNOWN.
mysql> select distinct qos from job_table LIMIT 5;
+------+
| qos |
+------+
| 0 |
+------+
1 row in set (1.18 sec)
mysql> select * from qos_tables;
ERROR 1146 (42S02): Table 'slurm.qos_tables' doesn't exist
mysql> select * from qos_table;
+---------------+------------+---------+----+--------+--------------------+-------------------+--------------------------+------------------+-------------------+---------------------------+----------------------+----------+-----------------+----------+-----------+----------+--------------+---------+----------+--------------+
| creation_time | mod_time | deleted | id | name | description
| max_jobs_per_user | max_submit_jobs_per_user | max_cpus_per_job |
max_nodes_per_job | max_wall_duration_per_job | max_cpu_mins_per_job |
grp_jobs | grp_submit_jobs | grp_cpus | grp_nodes | grp_wall |
grp_cpu_mins | preempt | priority | usage_factor |
+---------------+------------+---------+----+--------+--------------------+-------------------+--------------------------+------------------+-------------------+---------------------------+----------------------+----------+-----------------+----------+-----------+----------+--------------+---------+----------+--------------+
| 1279922694 | 1279922694 | 0 | 1 | normal | Normal QOS
default | NULL | NULL |
NULL | NULL | NULL |
NULL | NULL | NULL | NULL | NULL | NULL |
NULL | | 0 | 1 |
| 1279922916 | 1279922916 | 0 | 2 | high | high priority
| NULL | NULL | NULL |
NULL | NULL | NULL |
NULL | NULL | NULL | NULL | NULL |
NULL | | 100 | 1 |
| 1279922916 | 1288023714 | 0 | 3 | bump | devel preempt
| NULL | NULL | NULL |
NULL | NULL | NULL |
NULL | NULL | NULL | NULL | NULL |
NULL | | 1000 | 1 |
| 1316549150 | 1316549150 | 0 | 4 | low | low
| NULL | NULL | NULL |
NULL | NULL | NULL |
NULL | NULL | NULL | NULL | NULL |
NULL | | NULL | 1 |
+---------------+------------+---------+----+--------+--------------------+-------------------+--------------------------+------------------+-------------------+---------------------------+----------------------+----------+-----------------+----------+-----------+----------+--------------+---------+----------+--------------+
4 rows in set (0.00 sec)
mysql> select id,name,description from qos_table;
+----+--------+--------------------+
| id | name | description |
+----+--------+--------------------+
| 1 | normal | Normal QOS default |
| 2 | high | high priority |
| 3 | bump | devel preempt |
| 4 | low | low |
+----+--------+--------------------+
4 rows in set (0.00 sec)
I also have a different slurm 2.2.7 instance where this is being
record fine. So, I suspect this can be just fixed by upgrading. How
is the upgrade between 2.1.14 and 2.2.7? Any hints?
Thanks,
Chris
