bug #16
Behavior on concurrent wait / job submission
| Status: | rejected | Start date: | 06/13/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
This problem was already raised in an experience report for DRMAAv1, so we should cover it also here:
The DRMAA specification does not clarify whether some wait operation running in one thread should react to job submission
event in the other thread. This leads to ambiguity and makes this behavior implementation
dependant.
History
Updated by Peter Tröger over 10 years ago
- Status changed from submitted to rejected
OGF35 decision: waitAnyStarted() and waitAnyTerminated() take a job list as input, so this problem does not occur.
(Other formats not available in this archive.