[GE users] Problems with DRMAA and load sensors

templedf daniel.templeton at oracle.com
Tue Apr 20 19:22:37 BST 2010

By default, DRMAA adds a "-w e" to all job submissions.  The reasoning 
was that since DRMAA does not afford you much ability to deal with jobs 
stuck in a pending state, we should discourage unschedulable jobs from 
being submitted.


On 04/20/10 00:12, clemens69 wrote:
>> Hi all,
>> It seems that I have a problem using DRMAA in combination with load sensors.
>> We are using GE 6.1u6
>> Please let me describe my problem briefly: I am executing jobs on the
>> SGE via DRMAA. We defined some load sensors on our execution hosts which
>> return a list of key value pairs of resources. I want to constraint my
>> executed jobs to one of these resources, hence I set
>> JobTemplate#setNativeSpecification("-l foo=bar"), where foo is the
>> resource returned by the load sensor. This results always in a
>> Caused by: org.ggf.drmaa.DeniedByDrmException: error: no suitable queues
>> if the job is executed via DRMAA. On the other hand, when I execute
>> the job via qsub, it succeeds:
>> qsub -b y -l foo=bar echo hell world
>> Is there a known issue with 6.1u6 with respect do this problem or do i
>> miss something?
>> Best regards,
>> Lars Girndt
> Hello,
> this issue can be fixed by adding the option
> '-w n' to method 'setNativeSpecification()', which disables job-validation (this is default on command-line, hence these jobs are passed).
> regards,
> Clemens
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=254128
> To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].


To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].

More information about the gridengine-users mailing list