| Summary: | there is no suspend and transferring states in condor qmf objects | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Martin Kudlej <mkudlej> | |
| Component: | condor-qmf | Assignee: | grid-maint-list <grid-maint-list> | |
| Status: | CLOSED WONTFIX | QA Contact: | MRG Quality Engineering <mrgqe-bugs> | |
| Severity: | low | Docs Contact: | ||
| Priority: | low | |||
| Version: | 2.1 | CC: | croberts, matt, tmckay, tstclair | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | condor-7.8.2-0.1 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: QMF client views (using qpid-tool, for example) a Submission object's job totals.
Consequence: QMF clients could not view the totals for suspended and transferring_output job states.
Change: The QMF management schema was updated to add these new job states to the Submission class. The QMF schedd plug-in and Job Server were updated to also count these job states internally and pass the results to the modified API.
Result: QMF clients can view the totals for suspended and transferring_output job states.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 803731 (view as bug list) | Environment: | ||
| Last Closed: | 2016-05-26 20:22:42 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 803731 | |||
Currently, we can only add these stats to the submission object. Please a separate BZ for the scheduler and submitter objects which need to derive these from classad attributes from the schedd and collector respectively. Was this fixed in condor-7.6.7-0.2 just for submission object? If yes, is there new BZ for the scheduler and submitter objects? If no, please open new bug for scheduler and submitter objects. Based on a quick code review: Cumin currently touches the Submitter object in 3 places 1) The overview on the "Grid user" tab uses the Submitter object to summarize the user jobs. Currently this displays Running, Idle, and Held counts. Plenty of space here to add extra attributes. 2) Under Overview->Schedulers->Submitters, we also have a table of Submitters which shows Running, Idle, Held. Content here would have to be shortened to make Suspended fit the current minimum page width. I doubt we could fit TransferringOutput without being really creative (same issue as on Submission list tables). 3) In Overview->Schedulers->Submitters-><select one> we have Running, Idle, Held in a vertical stack on the Overview. Plenty of space here, too. And of course the Details tab lists the object content. These would be the places where Cumin would display values for Suspended and TransferringOutput from Submitter objects. Other than these displays, I don't believe Cumin references these values or has a reason to. I think the downside of not implementing them is that users see different information on the Submission tables as opposed to the places mentioned above. It might be possible to synthesize the numbers for a submitter by querying submissions (but we have discussed issues involved in going from submitters->submissions a separate Bug 703274) Could you please reply my questions from comment #3? This was only fixed for the submission objects. Comment #4 and #5 is a discussion to ascertain the necessity of those states to cumin. Feel free to raise separate BZ as indicated from comment #1.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: QMF client views (using qpid-tool, for example) a Submission object's job totals.
Consequence: QMF clients could not view the totals for suspended and transferring_output job states.
Change: The QMF management schema was updated to add these new job states to the Submission class. The QMF schedd plug-in and Job Server were updated to also count these job states internally and pass the results to the modified API.
Result: QMF clients can view the totals for suspended and transferring_output job states.
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs. |
Description of problem: $ qpid-tool qpid: show _scheduler_id_ Object of type: com.redhat.grid:scheduler:_data(bd2ad5ee-e92d-f62b-250f-e1518db1e8ef) Attribute 123 ================================================================================================== <snip/> TotalHeldJobs 0 TotalIdleJobs 0 TotalJobAds 16 TotalRemovedJobs 0 TotalRunningJobs 15 <snip/> qpid: show _suspended_submission_id_ show 238 Object of type: com.redhat.grid:submission:_data(34c745f2-febe-1dc8-53ce-6142c3b2bdb8) Attribute 238 ==================================================== jobserverRef 161 Name _X_#159 Owner condor QDate Mon Nov 21 09:19:22 2011 Idle 0 Running 0 Removed 0 Completed 0 Held 0 $ condor_q 159 -- Submitter: _X_ : <_x_:35875> : _X_ ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD 159.0 condor 11/21 04:19 3+20:25:16 S 0 9.8 wait.bat 1000000 Version-Release number of selected component (if applicable): condor-qmf-7.6.5-0.10 How reproducible: 100% Steps to Reproduce: 1. install and setup condor, qmf plugins for condor and qmf jobserver 2. get information about suspended jobs via qmf client, for example qpid-tool Actual results: There is not information about jobs in "Transferring output" and "Suspended" state in any QMF objects. Expected results: There will be information about jobs in "Transferring output" and "Suspended" state in all related QMF objects, for exmaple: TotalTransferringOutputJobs TotalSuspendedJobs in QMF scheduler object and Suspended TransferringOutput in QMF submission object.