Victor,
in your slurm.conf, you should have a line like this one
NodeName=n[1-4] Feature=knl Sockets=1 CoresPerSocket=68 State=UNKNOWN
at first, make sure your regular Xeon nodes do *not* have the 'knl' feature
i guess an other option is not to have the
NodeFeaturesPlugins=knl_generic
line on your regular Xeon nodes
(note that unless you specify an option, you will get some warnings
since all your slurm.conf are not identical)
Cheers,
Gilles
On 7/6/2017 2:38 AM, Victor Gamayunov wrote:
knl_generic plugin on non-KNL node
Hi,
i have a cluster with a mix of regular Xeon and KNL nodes. I use
knl_generic to switch KNL modes which works very well.
However, there is a side effect on non-KNL nodes: every time I
allocate a non-KNL node and specify a constraint (which has nothing to
do with KNL), the node is rebooted every time.
Is there a way do selectively disable the plugin on non-KNL nodes?
I looked at the code but couldn't quite figure out what forces the reboot.
Thanks
Victor
