Opened 17 years ago

Last modified 9 years ago

#57 new enhancement

IZ315: export context variables into job environment

Reported by: ernst Owned by:
Priority: low Milestone:
Component: sge Version: current
Severity: Keywords: execution
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=315]

        Issue #:      315              Platform:     All           Reporter: ernst (ernst)
       Component:     gridengine          OS:        All
     Subcomponent:    execution        Version:      current          CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     pollinger
          URL:
       * Summary:     export context variables into job environment
   Status whiteboard:
      Attachments:

     Issue 315 blocks:   61 61
   Votes for issue 315:


   Opened: Thu Jul 11 08:08:00 -0700 2002 
------------------------


(1)

According to discussions with Fritz, Andreas and Andy we saw that it
is helpful for our customers to export certain job context variables
into the job environment.

   qsub/qalter -ac ENV:variable=value

might be used to add such a special context variable into the job context.
The job will find the "variable" in its environment. If these special
context variables are used in combination with array jobs than the
environment variable will be found in the environment of each
array task.

Furthermore a cluster configuration parameter should be added which limits
the size of a job context ("max_env_ctx_size").

(This facility provides a workaround for issue #61)
---

(2)

In future it might be helpful to define some kind of array task specific
context and/or environment. Task specific variables do only apply for their
task. Special task context variables (see (1)) will only be exported into one
array task environment.

Further discussion has to take place before we implement such task special
variable list. Until now it is not obvious where such variables should
be stored.

   ------- Additional comments from sgrell Mon Dec 12 03:11:05 -0700 2005 -------
Changed subcomponent.

Stephan

Change History (0)

Note: See TracTickets for help on using tickets.