Custom Query (431 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (112 - 114 of 431)

Ticket Resolution Summary Owner Reporter
#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.
#504 fixed IZ2544: qmake should be upgraded to Make 3.80 elrond1999
Description

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

        Issue #:      2544             Platform:     All           Reporter: elrond1999 (elrond1999)
       Component:     gridengine          OS:        All
     Subcomponent:    clients          Version:      6.1u3            CC:    None defined
        Status:       NEW              Priority:     P3
      Resolution:                     Issue type:    ENHANCEMENT
                                   Target milestone: ---
      Assigned to:    roland (roland)
      QA Contact:     roland
          URL:
       * Summary:     qmake should be upgraded to Make 3.80
   Status whiteboard:
      Attachments:

     Issue 2544 blocks:
   Votes for issue 2544:


   Opened: Mon Apr 7 01:06:00 -0700 2008 
------------------------


I'm missing the $eval feature in the current qmake version (3.78). It's probably
not to hard to upgrade qmake to 3.8 or later. If this is not possible is it
possible to patch make myself? Do you have a ready patch that I can use somewhere?

   ------- Additional comments from andreas Mon Apr 7 01:38:38 -0700 2008 -------
I'm sorry, but we do not yet have such a patch.

Upgrading qmake to 3.80 or later is certainly possible, but to my knowledge
nobody is working on this right now. If you consider to pursue that I would
suggest to start by obtaining the source diff between 3.78 and 3.80 from the
make source tree. Based on that it might be possible to apply the change as a
patch (using patch(1) command) into SGE source tree.


   ------- Additional comments from rayson Mon Apr 7 21:05:19 -0700 2008 -------
I built qmake with gmake 3.8 a year ago. See:

http://gridengine.sunsource.net/servlets/ReadMsg?list=dev&msgNo=3016

Rayson


   ------- Additional comments from elrond1999 Tue Apr 8 01:10:51 -0700 2008 -------
Hi I tried to do what you said, but I was unable to put any SGE features into
make. It compiles and links with remote-sge.c but the resulting executable does
not understand sge options.. I probably did something wrong along the way :)
Maybe instead I need the 3.78 -> 3.81 make patch. Or the 3.78 ->
3.78-distributed patch.

   ------- Additional comments from rayson Tue Apr 8 05:56:38 -0700 2008 -------
Thanks for trying my changes.

I diff'ed 3.78 qmake vs 3.78 gmake, and I found that I missed one additional
additional in main.c. Without it SGE options are no handled by the new qmake.

int main (int argc, char ** argv)
#endif
{
  ...
  ...
  PATH_VAR (current_directory);

+  /* read and strip options for remote execution */
+  remote_options(&argc, &argv);

#ifdef WINDOWS32

  ...
  ...

Thanks,
Rayson


   ------- Additional comments from rayson Tue Apr 8 06:03:15 -0700 2008 -------
Typo (yup, just woke up a few minutes ago), should be:

"I diff'ed 3.78 qmake vs 3.78 gmake, and found that I missed a change in main.c.
Without it SGE options are not handled by the new qmake."

Also, you will need to add the function declaration:

extern void remote_options PARAMS ((int *p_argc, char **p_argv[]));

BTW, if unsure, you can always download 3.78.1 from GNU, and diff main.c against
the SGE version.

Rayson


   ------- Additional comments from elrond1999 Thu Apr 10 01:08:27 -0700 2008 -------
That did it I now have what seems like a working 3.81 qmake. I had to hack the
Makefile to make it include remote-sge.c/o, so I'm not sure I've done the
./configure correctly but at least it works now.
Note: See TracQuery for help on using queries.