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 if this thing.
As a good example, this is a task array submitted with no -binding parameter.
$> qstat -j 123 | grep bind
binding: NONE
mbind: NONE
binding 2467: node10=0,5
binding 2468: node11=0,9
binding 2469: node12=0,1:0,6:0,7:0,8
binding 2470: node12=1,0:1,7:1,8:1,9
binding 2471: node13=0,3
binding 2472: node14=1,0:1,7:1,8:1,9
binding 2473:
binding 2474:
binding 2471: node17=0,3
As you can see, there is no 'binding' defined for a job, but for a some reason
UGE scheduler binds the job. This very task-array is SMP 4 cores job, and as
you can see sometimes it binds to 4 cores, sometimes to 1 core, sometimes there
is no binding (which is right).
I did check the 'config' file of affected task ( on the node in a active_jobs
folder, the same folder contains trace file), and found that there is
'explicit' binding in the configuration file… I don't know from where it comes.
Any ideas?
Best regards,
Mikhail Serkov_______________________________________________
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users
