Thanks, Jeffrey. It looks like this limit has been changed to 42 on the
master branch of Slurm, so I suppose a future version of Slurm (19?) will
fix this.
__
*Jacob D. Chappell, CSM*
*Research Computing Associate*
Research Computing | Research Compu
For MySQL to use a text column as a primary key, it requires a limit on how
many bytes are significant. Just check through
src/plugins/accounting_storage/mysql/accounting_storage_mysql.c and you'll see
lots of primary keys with "(20)" indexing lengths specified.
With an extant database you ma
You can also use the influxdb profiling plugin I developed that’s included in
the latest slurm version. It will provide live cpu and memory usage per task,
step, host and job. You can then provide a grafana dashboard to display the
live metrics
Regards,
Carlos
Sent from my iPhone
> On 9 Dec 2
Would job profiling with HDF5 work as well?
https://slurm.schedmd.com/hdf5_profile_user_guide.html
Jacob
On Sun, Dec 9, 2018 at 4:17 PM Sam Hawarden
wrote:
> Hi Aravindh
>
> For our small 3 node cluster I've hacked together a per-node python script
> that collects current and peak cpu, memory
If you want to detect lost DIMMs or anything like that use a Node Health
Check script. I recommend and use this one: https://github.com/mej/nhc
It has an option to generate a configuration file that will watch way
more than you probably need, but if you want to know if something on
your nodes h
Hi all,
We've come across an issue recently with Slurm account names. Our center
uses fairly long Slurm account names, as they record various important
pieces of information about the account such as the user's unique id,
department, project name, etc. Consequently, our account naming structure
is
