Hi Todd, you might have seen the announcement about DRMAAv2 becoming an official OGF standard. 'Old DRMAA' had the problem you described. DRMAAv2 has a concept of session persistency, which leads to the demanded reusability of job identifiers. The workaround for 'old DRMAA' was to assume that job identifiers remain valid between sessions. For all implementations I know, this is a valid assumption, since the DRM system identifiers are used as DRMAA job identifiers. Best regards, Peter. P.S.: We have a strong interested in DRMAAv2 adoption for Condor. Please contact me if you see a change to make that happen. Am 08.02.2012 um 18:32 schrieb Todd Tannenbaum:
Hi DRMAA experts -
IIRC, last time I looked into DRMAA it used ephemeral job ids - in other words, when submitting a job via DRMAA you got back a handle to the job, but this handle was meaningless across a restart of the application (similar to a file descriptor). So if application X submits a job and then application X is restarted (e.g. the submit machine is rebooted), there was no guarantee that X could continue to monitor/manage the job.
Is the above still true? If so, is there a well-known work-around and/or are there plans to address the issue in a future DRMAA spec?
Thanks much, Todd
-- Todd Tannenbaum University of Wisconsin-Madison Center for High Throughput Computing Department of Computer Sciences -- drmaa-wg mailing list drmaa-wg@ogf.org https://www.ogf.org/mailman/listinfo/drmaa-wg