Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (22 - 24 of 431)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Ticket Resolution Summary Owner Reporter
#85 fixed IZ483: reporting of reason for job abort fy
Description

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

        Issue #:      483              Platform:     All           Reporter: fy (fy)
       Component:     gridengine          OS:        All
     Subcomponent:    execution        Version:      5.3p2            CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     pollinger
          URL:
       * Summary:     reporting of reason for job abort
   Status whiteboard:
      Attachments:

     Issue 483 blocks:
   Votes for issue 483:


   Opened: Wed Feb 5 08:11:00 -0700 2003 
------------------------


When a job exceeds one of the resource limits, say
h_rt, the job is killed with SIGKILL, however,
there is no clear indication as to why the job was
killed. None of the files in $SGE_JOB_SPOOL_DIR
provide any added information, so writing an
epilog does not help. The best we can do is guess
from the failed code (=100), and
end_time-start_time.

The enhancment being asked for is some kind of
reason as to why the job was killed, e.g.
(reason=limit_exceeded, limit=h_rt).

   ------- Additional comments from andreas Fri Apr 15 06:56:13 -0700 2005 -------
HOWTOFIX:
In case a job was terminated due to limit exeeded a new SSTATE_* such as
SSTATE_LIMIT_EXCEEDED is needed. Each time sge_execd initiates job termination
a flag must be set with that job. This will sge_execd to report
SSTATE_LIMIT_EXCEEDED for those jobs/tasks.

   ------- Additional comments from andreas Mon Jul 25 02:15:10 -0700 2005 -------
Changed execd logging in Maintrunk from Info to Warning to improve diagnosics.
Further improvements seem possible. Added related comments to
daemons/execd/execd_signal_queue.c

   ------- Additional comments from andreas Mon Aug 8 04:16:35 -0700 2005 -------
See issue 1743 for a reasonable 6.0 based workaround and an RFE how to generally
improve job diagnostics based oo job life-cycle information available in
reporting(5).

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

Stephan
#87 fixed IZ512: performance of non unique hashtables can be improved joga
Description

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

        Issue #:      512              Platform:     All           Reporter: joga (joga)
       Component:     gridengine          OS:        All
     Subcomponent:    qmaster          Version:      5.3p3            CC:    None defined
        Status:       STARTED          Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    joga (joga)
      QA Contact:     ernst
          URL:
       * Summary:     performance of non unique hashtables can be improved
   Status whiteboard:
      Attachments:

     Issue 512 blocks:
   Votes for issue 512:


   Opened: Mon Mar 24 05:49:00 -0700 2003 
------------------------


Non unique hash tables (module cull_hash) show bad
performance, if there is a huge amount of entries
for one hashkey (see also issue 493).

Their performance should be improved.

This can for example be accieved by setting a
unique hash key on the members of the non unique
object list.

Additional memory overhead should be analyzed and
carefully evaluated against performance improvements.

   ------- Additional comments from joga Tue Mar 30 04:23:27 -0700 2004 -------
started

   ------- Additional comments from sgrell Mon Dec 12 03:03:07 -0700 2005 -------
Changed the subcomponent.

Stephan

   ------- Additional comments from ernst Tue Aug 19 02:55:53 -0700 2008 -------
Isn't this already implemented?
#94 invalid IZ553: Admin guide: Moved object references from pe/ckpt into queue ernst
Description

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

        Issue #:      553              Platform:     All       Reporter: ernst (ernst)
       Component:     gridengine          OS:        All
     Subcomponent:    doc              Version:      6.0          CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    FEATURE
                                   Target milestone: ---
      Assigned to:    andreas (andreas)
      QA Contact:     skonta
          URL:
       * Summary:     Admin guide: Moved object references from pe/ckpt into queue
   Status whiteboard:
      Attachments:

     Issue 553 blocks:
   Votes for issue 553:


   Opened: Thu May 15 04:49:00 -0700 2003 
------------------------


The attribute set of the pe object, checkointing
environment and queue has been
changed. These changes will be available with the
next major release (6.0) of
SGE/EE.

PE object
---------
The attribute "queue_list" has been removed from
pe object.
The "queue_list" attribute made it possible to
define a relation between one pe
enviropnment and multiple queue objects.

CKPT object
-----------
Also here the attribute "queue_list" has been removed.
The "queue_list" attribute made it possible to
define a relation between one
ckpt interface and multiple queue objects.

QUEUE object
------------
Two attributes have been added to the queue
specification: "pe_list" and
"ckpt_list". These new lists may contain a list of
pe/ckpt names or the
keyword "NONE". Both lists make it possible to
define relations between
one queue object and multiple pe environments/ckpt
interfaces.

The definition of the qtype attibute has been
changed. The formerly supported
types parallel and checkpointing are deprecated. A
queue is implicitely of
type parallel/checkpointing if there is a parallel
environment or a
checkpointing interface specified for this queue
instance in
"pe_list"/"ckpt_list".
Currently allowed values for qtype are BATCH
and/or INTERACTIVE or the
keyword NONE. Default value for new queues is
BATCH and INTERACTIVE

Some Examples
-------------

a)

   Old configuration:

      QUEUE1:
         qtype PARALLEL

      PE1:
         queue_list QUEUEU1

   New configuration:

      QUEUE1:
         qtype NONE
         pe_list PE1

      PE1:

b)

   Old configuration:

      QUEUE1:
         qtype BATCH CHECKPOINTING

      CKPT1:
         queue_list QUEUEU1

   New configuration:

      QUEUE1:
         qtype BATCH
         ckpt_list CKPT1

      CKPT1:

   ------- Additional comments from andreas Tue Jul 20 10:10:54 -0700 2004 -------
Changed summary.

   ------- Additional comments from andreas Thu Oct 21 08:37:22 -0700 2004 -------
Assign User/Admin/Install issues to Mark O'Brien.

   ------- Additional comments from surajp Mon Mar 23 01:53:25 -0700 2009 -------
Reassigning issue to Sandra.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Note: See TracQuery for help on using queries.