Hi,
In exchange for Slurm automatically handling database setup (and
reconfiguration when you upgrade to a newer version of Slurm), you
have to allow it to do whatever it wants to do with its tables.
Rather than adding (or reusing) an existing column in a table, I
would suggest creating new tables with names such as
"local_clusterName_job_table_extension" that have only your added
columns and appropriate keys. These tables should persist over
(most?) Slurm upgrades.
Andy
On 05/12/2015 07:27 AM, Anatoliy
Kovalenko wrote:
Usage of the "deleted" column in clusterName_job_table
table
We have added to the SLURM clusterName_job_table 1 custom
column. But when we restart slurmdbd , it is deleted. Why this
happens and is it possible to modify SLURM db (tables) without
disrupting SLURM work?
We have also noticed that in table clusterName_job_table
there is a column called "deleted". Is it used by SLURM at any
moment? Is this column (deleted) anyhow related to task
archival? If it is unused - can we use for our custom
purposes and sometimes put "1" there instead of 0? will it
anyhow affect SLURM work?
