Opened 10 years ago
Closed 7 years ago
#720 closed enhancement (wontfix)
IZ3143: Request multiple slots without using a PE
Reported by: | maritac | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.2u3 |
Severity: | minor | Keywords: | scheduling |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=3143]
Issue #: 3143 Platform: All Reporter: maritac (maritac) Component: gridengine OS: All Subcomponent: scheduling Version: 6.2u3 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: ENHANCEMENT Target milestone: --- Assigned to: andreas (andreas) QA Contact: andreas URL: * Summary: Request multiple slots without using a PE Status whiteboard: Attachments: Issue 3143 blocks: Votes for issue 3143: Opened: Wed Sep 30 11:22:00 -0700 2009 ------------------------ Currently, when requesting multiple slots for a job, it's necessary to configure and use a parallel environment: $ qsub -l slots=2 ./simple.sh Unable to run job: "job" denied: use parallel environments instead of requesting slots explicitly. Exiting. I have some SGE users who would like the ability to request multiple slots without being required to use a parallel environment. ------- Additional comments from reuti Thu Oct 1 04:49:41 -0700 2009 ------- Simple question: why? Not requesting a PE would let SGE in the dark whether they all should be located on one and the same machine, or multiple machines. And if you got multiple machines: how to tell the jobscript where to find them, when there is no pe_hostfile created? If it's just for SMP jobs, you can use the default setting of a new PE without any start/stop_proc_args. Whether someone request: -l slots=5 or -pe smp 5 is not much of a difference and would indicate clearly to SGE that it's a parallel job and how to handle additional resource requests.
Change History (1)
comment:1 Changed 7 years ago by dlove
- Resolution set to wontfix
- Severity set to minor
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
As Reuti said.