| Summary: | configuration hash | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | Yann <yann.sagon> |
| Component: | Configuration | Assignee: | Carlos Tripiana Montes <tripiana> |
| Status: | RESOLVED INFOGIVEN | QA Contact: | |
| Severity: | 4 - Minor Issue | ||
| Priority: | --- | CC: | tripiana |
| Version: | 22.05.3 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | Université de Genève | Alineos Sites: | --- |
| Atos/Eviden Sites: | --- | Confidential Site: | --- |
| Coreweave sites: | --- | Cray Sites: | --- |
| DS9 clusters: | --- | HPCnow Sites: | --- |
| HPE Sites: | --- | IBM Sites: | --- |
| NOAA SIte: | --- | OCF Sites: | --- |
| Recursion Pharma Sites: | --- | SFW Sites: | --- |
| SNIC sites: | --- | Linux Distro: | --- |
| Machine Name: | CLE Version: | ||
| Version Fixed: | Target Release: | --- | |
| DevPrio: | --- | Emory-Cloud Sites: | --- |
|
Description
Yann
2022-10-11 02:31:58 MDT
Hi Yann, > I was wondering what are the files included in the conf hash check? Only slurm.conf. > I guess the file acct_gather.conf isn't included as it seems impossible to > have the same file for every node as the file depends for example on ipmi > sensors. Or is there a way to list all the nodes in this file so we can > ensure the file is identical on the whole cluster as well, like we do for > the gres.conf file. acct_gather.conf is allowed to be different for each node, to adapt it to the underlying HW, as you have mentioned. We don't have the need to specify all nodes in a single acct_gather.conf as slurmctld doesn't really need to know the exact underlying plugin the node is using to grab the metrics. gres.conf needs to be a general one with all nodes in it because slurmctld needs to know all the cluster GRES, so it can properly schedule the jobs. I'm directly marking the bug as info given but if you need further assistance please reopen it and tell us your thoughts. Regards, Carlos. Thanks for the information Best Yann |