Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (139 - 141 of 431)

Ticket Resolution Summary Owner Reporter
#495 fixed IZ2530: execd: "ptf complains: Job does not exist" message in log file jogoodma
Description

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

        Issue #:      2530             Platform:     All      Reporter: jogoodma (jogoodma)
       Component:     gridengine          OS:        Linux
     Subcomponent:    execution        Version:      6.1u3       CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    pollinger (pollinger)
      QA Contact:     pollinger
          URL:
       * Summary:     execd: "ptf complains: Job does not exist" message in log file
   Status whiteboard:
      Attachments:

     Issue 2530 blocks:
   Votes for issue 2530:  5


   Opened: Thu Mar 20 08:32:00 -0700 2008 
------------------------


This issue may be a duplication of
http://gridengine.sunsource.net/issues/show_bug.cgi?id=1806.

I'm seeing the same type of warning messages.  In the execution host messages
file I have:

reaping job "54988" ptf complains: Job does not exist

and then 1 second later in the qmaster file I have:

"job 54988.1 finished on host <hostname>"

I can reproduce the problem using the sleeper.sh script similar to what is
described in 1806.  Setting the sleep time to 1 doesn't result in any warning
messages.   The jobs do complete normally with correct output; however, every
couple of weeks I will experience a complete queue lockup.  Jobs will be shown
as running but nothing is running on the exec host.  Killing the jobs removes
them from the queue but the next jobs that fill the slots get stuck in the same
manner.  Restarting SGE is the only solution I have found when this problem
occurs.  No other error messages have been observed in the logs to indicate a
separate problem.

I've have reproduced this with a single master/exec host setup running RHEL 5
and a separate master and exec host setup with both hosts running RHEL 4.  All
setups were tested with fresh installs of 6.1u3.
#496 fixed IZ2533: qconf -mrqs adds extra space and linebreak, which cannot be read back wig
Description

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

        Issue #:      2533             Platform:     All      Reporter: wig (wig)
       Component:     gridengine          OS:        Linux
     Subcomponent:    clients          Version:      6.1u3       CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    roland (roland)
      QA Contact:     roland
          URL:
       * Summary:     qconf -mrqs adds extra space and linebreak, which cannot be read back
   Status whiteboard:
      Attachments:

     Issue 2533 blocks:
   Votes for issue 2533:


   Opened: Fri Mar 21 13:11:00 -0700 2008 
------------------------


qconf -mrqs: Problems to read it’s own output:
If you try to edit a rule in non SGE_SINGLE_LINE mode, an added space
and line break in the "long" limits leads to
errors when you store and exit the editor (even
without changing a single character).

$ qconf -mrqs
{
name frcq_limit_550_usage
description Limit emulator slot usage to 2
enabled TRUE
limit users * projects frcq hosts muc-ax4x.micronas.com, \
muc-ax5x.micronas.com to axis_slots_550=2
}

---> returns:

unknown attribute name "muc-ax5x.micronas.com"
each value in the attribute value list in line 6 should end with
"<NEWLINE>"
unrecognized characters after the attribute values in line 6: "to"
each value in the attribute value list in line 6 should end with "}"

The \ is not recognized and both space and \ have to be removed
and all of the limit has to be on one line
before one can write back the rules successfully.
#503 fixed IZ2542: Allow users to limit concurrent array job task execution craffi
Description

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

        Issue #:      2542             Platform:     All           Reporter: craffi (craffi)
       Component:     gridengine          OS:        All
     Subcomponent:    scheduling       Version:      current          CC:    None defined
        Status:       STARTED          Priority:     P2
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: Maintrunk
      Assigned to:    andreas (andreas)
      QA Contact:     andreas
          URL:
       * Summary:     Allow users to limit concurrent array job task execution
   Status whiteboard:
      Attachments:

     Issue 2542 blocks:
   Votes for issue 2542:


   Opened: Sun Apr 6 07:17:00 -0700 2008 
------------------------


Summary:
 - This RFE requests a way for users (who do not have administrative access to
policy and RQS settings) to self-throttle the number of concurrent array tasks
executing at any given time.


In relation to these existing Enhancement issues:
http://gridengine.sunsource.net/issues/show_bug.cgi?id=2147
http://gridengine.sunsource.net/issues/show_bug.cgi?id=1276

The desired behavior is the following:

- Allow a user to limit the number of concurrent executing array tasks

Issue:

- Users have been trained to use array tasks to reduce SGE load
- Users who do this typically submit very large array jobs via qsub
- Users want to throttle concurrent execution of tasks to a fixed value
- This "self throttle" control is desired at the user level (not policy or RQS
level)

A "task" target for resource quotas has already been written up in #2147 - this
RFE asks for an extention to the "-t" switch of qsub:

 Existing array task syntax:

   -t n[-m[:s]]

 Proposed array task syntax:

  -t n[-m[:s]] -tc <INT>

.. where "-tc" is shorthand for "task concurrency". The default value should
place no constraint on executing tasks. If present, <INT> will specify the upper
bound of tasks that are allowed to execute simultaneously.

   ------- Additional comments from andreas Mon Apr 7 00:34:00 -0700 2008 -------
Good RFE!

It should be possible to reuse our existing RQS code infrastructure for it.

I raise it to P2 as this was repeatedly requested by the community. It will
improve SGE resource control significantly.

   ------- Additional comments from andreas Mon Apr 7 00:39:41 -0700 2008 -------
Target milestone obviously must be past 6.2.

   ------- Additional comments from templedf Mon Dec 22 23:43:05 -0700 2008 -------
Expanded platform to all.
Note: See TracQuery for help on using queries.