I would be very cautious when trying to override or use the database
schema directly as it changes quite regularly. There is no guarantee
accessing a Slurm table directly today in a certain fashion will work in
the next major release.
On 05/13/15 10:17, Bruce Roberts wrote:
I believe it is used when determining the last submitted job when
modifying a job as well as when archiving jobs, at least that is what
the code says.
On 05/13/15 10:12, Andy Riebs wrote:
No, I don't know how it's used. Anyone else care to answer?
Andy
On 05/13/2015 12:26 PM, Anatoliy Kovalenko wrote:
Re: [slurm-dev] Re: Usage of the "deleted" column in
clusterName_job_table table
Thanks for your advice about "new table". However it will a bit
difficult to support it in our case. Still, we need to know answer
to our question about "deleted" column in job_table - do you maybe
know how it is used?
2015-05-12 16:03 GMT+03:00 Andy Riebs <[email protected]
<mailto:[email protected]>>:
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:
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?
