We the same issue on our cluster. I looked into the code and from what I understand there are two threads that disagree on the available complexes.
Thread 1 the scheduler finds a host that is suitable and schedules the job. Then thread 2 the dispatcher checks its records but finds that “resources no longer available”. And returns the job to the scheduler. So they disagree on the amount of free resources on a host. - Are Sent from my mobile, sorry for the typos. 15. mai 2018 kl. 00:43 skrev Joshua Baker-LePain <j...@salilab.org<mailto:j...@salilab.org>>: On Mon, 14 May 2018 at 10:37am, Daniel Povey wrote I wonder if deleting that execution host and adding it back again might work around your issue. This issue showed up on multiple hosts. so I don't think that would help. The issue also survived a restart of SGE. -- Joshua Baker-LePain QB3 Shared Cluster Sysadmin UCSF _______________________________________________ users mailing list users@gridengine.org<mailto:users@gridengine.org> https://gridengine.org/mailman/listinfo/users
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
