Conference call - Sep 8th - 19:00 UTC
Dear all, the next DRMAA phone conference is scheduled on Sep 8th, at 19:00 UTC. The phone conference line is sponsored by Oracle. Please consult the following page for dial-in numbers from your country: http://www.intercall.com/oracle/access_numbers.htm The conference code is 6513037. The security code is DRMAA (37622). Preliminary meeting agenda: 1. JobInfo::jobTemplate vs. job monitoring attributes (check Google spreadsheet) 2. Sanity check for OS type description (check http://tinyurl.com/25cy9u7 ) 3. Proposal for new JobInfo attributes: priority and memory consumption (check Google spreadsheet) 4. Is SGE really not able to distinguish between user mode CPU time and system mode CPU time ? (check Google spreadsheet) 5. Collaborative editing of Google spreadsheet Google spreadsheet: http://spreadsheets.google.com/ccc?key=0AqyvnBscJNqxcnJBSUs5dXRrU29EUVhGOGth... Best regards, Peter.
Participants: Mac McCalla & Marion King (Hess Oil), Roger, Dan, Peter - Meeting secretary: Peter - Discussion of Hess Oil issue with DRMAAv1 interface - SGE can put jobs into error state on abnormal conditions, which allows to continue it after manual fixing - DRMAAv1 has no concept for this, implementation currently expresses the error jobs as still running, which makes detection difficult - Proposal for DRMAAv2: Map such jobs to SUSPENDED state, use subState concept to express detailed error condition, transition back to RUNNING possible in the DRMAA model - Hess Oil use case: simulation task farming, array jobs - Discussion on job history with persistent sessions - Agreed semantic is (still) that jobs might disappear between session usage - On the other side, implementation can also keep history of terminated jobs in the session - Important to not exclude this possibility in the spec layout
2. Sanity check for OS type description (check http://tinyurl.com/25cy9u7 )
.- Looks good for Roger, keep it as it is.
3. Proposal for new JobInfo attributes: priority and memory consumption (check Google spreadsheet)
- Short research showed that priority is always scheduling priority for all jobs of this user - Agreed to add priority to JobTemplate and JobInfo - Semantic of memory consumption information in the different systems still unclear - delayed
4. Is SGE really not able to distinguish between user mode CPU time and system mode CPU time ? (check Google spreadsheet) 5. Collaborative editing of Google spreadsheet
Google spreadsheet: http://spreadsheets.google.com/ccc?key=0AqyvnBscJNqxcnJBSUs5dXRrU29EUVhGOGth...
Dropped due to time issues. Best, Peter.
participants (1)
-
Peter Tröger