Custom Query (1181 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (133 - 135 of 1181)

Ticket Resolution Summary Owner Reporter
#33 fixed IZ243: Memory leak in sge_schedd ernst
Description

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

        Issue #:      243              Platform:     All              Reporter: ernst (ernst)
       Component:     gridengine          OS:        All
     Subcomponent:    kernel           Version:      5.3                 CC:    None defined
        Status:       VERIFIED         Priority:     P3
      Resolution:     FIXED           Issue type:    DEFECT
                                   Target milestone: not determined
      Assigned to:    ernst (ernst)
      QA Contact:     andreas
          URL:
       * Summary:     Memory leak in sge_schedd
   Status whiteboard:
      Attachments:

     Issue 243 blocks:
   Votes for issue 243:


   Opened: Mon Apr 29 05:20:00 -0700 2002 
------------------------


Memory leak in sge_schedd

According to the code discussion with Patrik Koch we have identified
several errors in sge_schedd process:

> Code discussion
> ===============
>
> - sge_process_events.c, event_handles_default_scheduler()
>   line 650: if (is_running)... possible???
>   How can it be that tasks of a newly added job are already running?
>   And a few lines above at the beginning of sgeE_JOB_ADD:
>   How can the job and the relevant task be already in the joblist?
>   line 653: at_inc_job_counter() leaves priority_group_list or
>     user list (PGR_subordinate_list) unsorted!

I also would assume that the job/task should not already be in the
joblist. I will fix it.

> - sge_process_events.c, event_handles_default_scheduler()
>   line 1559: sgeE_JATASK_DEL
>   if ja_task is enrolled and the only task of the job -> job is
>       removed from lists.job_list
>   if ja_task is not enrolled but the only task of the job -> job is
>       not removed from lists.job_list ???

I will fix it. (==> Memory leak)

> - sge_job_schedd.c, split_job()
>   line 508: job=NULL;
>   line 525: remaining tasks -> lCopyElem(job) ==>> LERROR !
>   line 567: if (job) -> always false !
>   ??? What should be done with remaining tasks? Are they possible?

I don't think that remaining tasks are possible in the moment. If they
occure, they should stay in the source list if they are not needed for
scheduling decisions or if it is not necessary to generate scheduling
messages for the "qstat -j" output.

I will fix the error you found.

   ------- Additional comments from ernst Mon Apr 29 05:21:54 -0700 2002 -------
Started.

   ------- Additional comments from ernst Mon Apr 29 06:33:29 -0700 2002 -------
Fixed.

   ------- Additional comments from ernst Wed May 8 03:24:11 -0700 2002 -------
Review has been done by Andreas.
#867 duplicate IZ245: Need a naming convention for all resource bundles rhierlmeier
Description

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

        Issue #:      245          Platform:     Sun           Reporter: rhierlmeier (rhierlmeier)
       Component:     hedeby          OS:        All
     Subcomponent:    util         Version:      current          CC:    None defined
        Status:       NEW          Priority:     P2
      Resolution:                 Issue type:    ENHANCEMENT
                               Target milestone: 1.0u5next
      Assigned to:    marcingoldyn (marcingoldyn)
      QA Contact:     rhierlmeier
          URL:
       * Summary:     Need a naming convention for all resource bundles
   Status whiteboard:
      Attachments:


     Issue 245 blocks:
   Votes for issue 245:     Vote for this issue


   Opened: Thu Nov 29 02:33:00 -0700 2007 
------------------------


   We have a lot of "dead" messages in our resource bundles. We need a testsuite
   test (or an ant task) which finds unused messages.
               ------- Additional comments from crei Mon Dec 3 01:56:57 -0700 2007 -------
   already submitted

   *** This issue has been marked as a duplicate of 208 ***
               ------- Additional comments from rhierlmeier Wed Feb 27 06:42:59 -0700 2008 -------
   With the fix of this issue we should cleanup the resource bundles.

   We need a naming convention for all resource bundles. We suggest that the
   name of the resource bundle is the name of the package without com.sun.grid.grm.

   We have to check what naming conventions the resource bundles have. May be dots
   are not allowed in it.

   service-impl.properties -> resource bundle for package com.sun.grid.grm.service.
               ------- Additional comments from rhierlmeier Thu Feb 28 02:47:26 -0700 2008 -------
   Reassigned
               ------- Additional comments from rhierlmeier Thu Feb 28 03:24:37 -0700 2008 -------
   It's now a task
               ------- Additional comments from crei Wed Aug 6 05:03:07 -0700 2008 -------
   Dead message detections filed as testsuite issue #220

   Still a hedeby task is the resource bundle naming convention task
               ------- Additional comments from crei Wed Aug 6 05:05:08 -0700 2008 -------
   Renamed Issue summary and changed subcomponent - issue is no testsuite issue
               ------- Additional comments from rhierlmeier Wed Aug 6 06:50:53 -0700 2008 -------
   It's a cleanup issue for future releases (ENHANCEMENT).
   Should be in the subcomponents infrastructure.
               ------- Additional comments from rhierlmeier Wed Nov 25 07:21:10 -0700 2009 -------
   Milestone changed
#35 fixed IZ245: qhost -l h=<hostname> does not work andreas
Description

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

        Issue #:      245              Platform:     All          Reporter: andreas (andreas)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      V53_alpha1      CC:
                                                                            [_] uddeborg
                                                                            [_] Remove selected CCs
        Status:       REOPENED         Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: 6.0
      Assigned to:    andreas (andreas)
      QA Contact:     roland
          URL:
       * Summary:     qhost -l h=<hostname> does not work
   Status whiteboard:
      Attachments:
                      Date/filename:                             Description:                  Submitted by:
                      Wed Jan 30 06:40:00 -0700 2008: patch.diff That''s the diff (text/plain) andreas

     Issue 245 blocks:
   Votes for issue 245:


   Opened: Tue May 7 07:21:00 -0700 2002 
------------------------


DESCRIPTION:
Though one would expect it to work the 'hostname'
attribute can't be used
with qhost for selecting particular hosts.

WORK AROUND:
# qhost | grep <hostname>

SUGGESTED FIX:
The 'hostname' attribute is not in the 'host'
complex but in the 'queue' complex. For this
reason an exechost does not have a 'hostname'
attribute.To fix this problem the 'hostname'
attribute must be moved into the 'host' complex
and the host information must be filled into this
complex attribute from the exechost.

   ------- Additional comments from uddeborg Fri Jun 17 01:55:57 -0700 2005 -------
This problem still remains in 6.0u5 beta

   ------- Additional comments from sgrell Tue Dec 6 08:37:08 -0700 2005 -------
Changed subcomponent.

Stephan

   ------- Additional comments from roland Tue Nov 14 08:29:51 -0700 2006 -------
WORKAROUND:
qhost -h hostlist

   ------- Additional comments from dom Tue Jan 29 11:57:54 -0700 2008 -------
fixed in maintrunk and V61_BRANCH

   ------- Additional comments from andreas Wed Jan 30 06:39:15 -0700 2008 -------
Fix

http://gridengine.sunsource.net/servlets/ReadMsg?list=cvs&msgNo=9557

appears problematic. The attached patch could solve the actual problem.

   ------- Additional comments from andreas Wed Jan 30 06:40:44 -0700 2008 -------
Created an attachment (id=147)
That''s the diff
Note: See TracQuery for help on using queries.