Opened 17 years ago

Last modified 11 years ago

#147 new enhancement

IZ873: make use of drmaa_init() 'contact' for library bootstrapping

Reported by: andreas Owned by:
Priority: normal Milestone:
Component: sge Version: 6.0beta
Severity: Keywords: drmaa


[Imported from gridengine issuezilla]

        Issue #:      873              Platform:     All           Reporter: andreas (andreas)
       Component:     gridengine          OS:        All
     Subcomponent:    drmaa            Version:      6.0beta          CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     templedf
       * Summary:     make use of drmaa_init() 'contact' for library bootstrapping
   Status whiteboard:
                      Date/filename:                            Description:                                             Submitted by:
                      Thu Feb 28 09:17:00 -0700 2008: 2505.diff The diff should fix the leak in V61_BRANCH. (text/plain) andreas

     Issue 873 blocks:
   Votes for issue 873:

   Opened: Wed Mar 17 04:29:00 -0700 2004 

Current DRMAA library bootstrapping does not make
use of the contact string argument of
drmaa_init(). Instead the following env vars
are used for this purpose


only $SGE_ROOT is duty. If $SGE_CELL is not set
'default' is assumed. If $SGE_QMASTER_PORT is not
set the 'sge_qmaster' service must resolve
a tcp port number instead.

The Grid Engine 6.0 contact string could be
defined as


then a string of that format would have to be
returned by drmaa_get_contact() and be accepted by

Though the current behaviour of having
drmaa_get_contact() return an empty string "" and
then if "" is forwarded to drmaa_init() having it
contact the default DRM system is compliant with
DRMAA spec. Nevertheless better defining that
interface is desirable.

   ------- Additional comments from andreas Wed Mar 17 04:32:37 -0700 2004 -------
Changed version.

   ------- Additional comments from templedf Fri Apr 23 02:26:50 -0700 2004 -------
I will take a deeper look at this one.  What's wrong is not obvious.
The JAPI diag dstring appears to be passed around properly.  We're
probably just not properly accounting for a return code from some
other SGE call.

   ------- Additional comments from andreas Thu Feb 28 09:17:59 -0700 2008 -------
Created an attachment (id=152)
The diff should fix the leak in V61_BRANCH.

   ------- Additional comments from andreas Thu Feb 28 09:22:22 -0700 2008 -------
Please ignore the attachment. It belongs actually to issue #2505.

Change History (0)

Note: See TracTickets for help on using tickets.