[GE users] -sync y with DRMAA

Rayson Ho rayrayson at gmail.com
Thu May 17 15:37:29 BST 2007


    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some special characters may be displayed incorrectly. ]

Yup... me too...

BTW, let's continue the discussion on the DRMAA list on the blocking
behavior of runJob(), and we will update this list later on.

Rayson



On 5/17/07, Daniel Templeton <Dan.Templeton at sun.com> wrote:
> And this time of day. ;)
>
> Daniel
>
> Rayson Ho wrote:
> > Thanks... I just saw your message.
> >
> > BTW, you are also up at this time of the day! :O
> >
> > Rayson
> >
> >
> > On 5/17/07, Daniel Templeton <Dan.Templeton at sun.com> wrote:
> >> Rayson,
> >>
> >> While it isn't explicitly in the spec, the intention of the runJob() and
> >> runBulkJobs() routines is that they do not block waiting for job
> >> finish.  I will bring the issue up on the DRMAA mailing list as
> >> something that needs to be clarified.
> >>
> >> Daniel
> >>
> >> Rayson Ho wrote:
> >> > Dan,
> >> >
> >> > I just read issue 2253... Is it possible for the DRMAA layer to
> >> > quietly wait for the job when it finds the existance of -sync??
> >> >
> >> > Rayson
> >> >
> >> > http://gridengine.sunsource.net/issues/show_bug.cgi?id=2253
> >> >
> >> >
> >> > On 5/16/07, Daniel Templeton <Dan.Templeton at sun.com> wrote:
> >> >> The reason for the error is that
> >> >> the -sync option is localized to qsub; the qmaster doesn't know
> >> anything
> >> >> about it.  qsub translates it into a wait() call.  It's a flaw that
> >> >> DRMAA allowed the -sync option to be passed to the qmaster.  I'll
> >> look
> >> >> into it and file a bug.
> >> >>
> >> >> Daniel
> >> >>
> >> >> Jeff White wrote:
> >> >> > When I submit a job with "-sync y" in the native specification of a
> >> >> > JobTemplate I get
> >> >> >
> >> >> > org.ggf.drmaa.DeniedByDrmException: Unknown option -sync y
> >> >> >
> >> >> > Am I correct in assuming this option doesn't work with DRMAA and I
> >> >> > must use the synchronize() method instead? In my case I have a
> >> >> > separate thread that uses wait(JOB_IDS_SESSION_ANY) to process
> >> >> > completed jobs. It may be convenient to have runJob() be able to be
> >> >> > synchronous itself. I'm guessing this is not feasible.
> >> >> >
> >> >> > thanks,
> >> >> > jeff
> >> >> >
> >> >> >
> >> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> >> >> > For additional commands, e-mail:
> >> users-help at gridengine.sunsource.net
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> >> >> For additional commands, e-mail: users-help at gridengine.sunsource.net
> >> >>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> >> > For additional commands, e-mail: users-help at gridengine.sunsource.net
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> >> For additional commands, e-mail: users-help at gridengine.sunsource.net
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> > For additional commands, e-mail: users-help at gridengine.sunsource.net
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list