Hello Everyone,
I've found a strange issue with core-binding behaviour on a cluster I'm working
on.
The thing is that for a some reason Scheduler binds the job even if it's not
requested.
I did check:
client/server side JSV
job classes
request file
There are no traces i
Hi Mikhail
That is indeed strange and the support request is handled properly in the
support portal. Things I can imagine: You are using host resources which
are requesting cores implicitly when requested (having cores attached with
topology masks) or you are running into an rare strtok() issue
