Opened 12 years ago
Last modified 10 years ago
#578 new feature
IZ2748: Jobs with no suitable queues at all should be easier detect
Reported by: | reuti | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | sge | Version: | 6.1u5 |
Severity: | Keywords: | clients | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2748]
Issue #: 2748 Platform: All Reporter: reuti (reuti) Component: gridengine OS: All Subcomponent: clients Version: 6.1u5 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: FEATURE Target milestone: --- Assigned to: roland (roland) QA Contact: roland URL: * Summary: Jobs with no suitable queues at all should be easier detect Status whiteboard: Attachments: Issue 2748 blocks: Votes for issue 2748: Opened: Thu Oct 2 04:14:00 -0700 2008 ------------------------ As a follow up of issue 2731: 2) After any -now y job timed out, check whether there were suitable queues at all and give the correct error message (Timeout or NoSuitableQueue). Good suggestion. You can bring that further: "qalter -w [pev]" or "qstat -j" should print an easy to understand message that a job cannot be schedule at all according to the current config. In addition "qstat" should have an option to identify quickly all jobs in the cluster which are not runnable at all.
Note: See
TracTickets for help on using
tickets.