IZ2078: Add scheduling and execution timeout for interactive and batch jobs
|Reported by:||fkoganf||Owned by:|
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2078]
Issue #: 2078 Platform: All Reporter: fkoganf (fkoganf) Component: gridengine OS: All Subcomponent: scheduling Version: 6.0u8 CC: None defined Status: NEW Priority: P2 Resolution: Issue type: ENHANCEMENT Target milestone: --- Assigned to: sgrell (sgrell) QA Contact: andreas URL: * Summary: Add scheduling and execution timeout for interactive and batch jobs Status whiteboard: Attachments: Issue 2078 blocks: Votes for issue 2078: Opened: Thu Jun 22 14:18:00 -0700 2006 ------------------------ Following up a conversation in email@example.com, I'm logging this RFE. Ron Chen wrote: ---- The timeout feature makes sense, and if you want to request it to be added to the next version of SGE, you can enter an enchancement request to the issue DB: http://gridengine.sunsource.net/servlets/ProjectIssues ---- So I'm responding with this request: We're running a large SGE 6.0u8 installation (hundreds of nodes). Recently a lot of users started asking for a timeout feature. That is, submit a job and make sure that it returned after certain period of time. Or submit a job and make sure that the submission command returns within a specified timeout if it cannot be executed right away. Something like: # returns in 10 minutes (timeout) $ qsub -to 600 some_job # qrsh returns an error message if the job hasn't been scheduled to run in 5 minutes (pending timeout) $ qrsh -now no -pt 300 some_job This seems like a useful feature that a lot of users would benefit of. It, in fact, would add elements of real-time scheduling, greatly increasing the appeal of SGE for many applications. -- Felix Kogan, D.E.Shaw & Co ------- Additional comments from templedf Mon Jan 12 13:47:51 -0700 2009 ------- You can find more details in the original message thread, here: http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=27350
Change History (0)
Note: See TracTickets for help on using tickets.