Red Hat Bugzilla – Full Text Bug Listing
|Summary:||RFE add support to keep a claim alive for DAG Submissions.|
|Product:||Red Hat Enterprise MRG||Reporter:||Timothy St. Clair <tstclair>|
|Status:||CLOSED WONTFIX||QA Contact:||MRG Quality Engineering <mrgqe-bugs>|
|Version:||Development||CC:||matt, mkudlej, tstclair|
|Target Milestone:||---||Keywords:||FutureFeature, TestOnly|
|Fixed In Version:||condor-7.8.2-0.3||Doc Type:||Rebase: Enhancements Only|
Important: if this rebase also contains *bug fixes* (or contains only bug fixes), select the correct option from the Doc Type drop-down list. Rebase package(s) to version: condor-7.8 series Highlights and notable enhancements: When submitting DAGMan jobs users can now supply a +KeepClaimIdle parameter which allows a claim to stay active during the interim period where condor_dagman is submitting new jobs. This enables higher throughput in cases where claims are relinquished prior to new jobs being submitted.
|Last Closed:||2016-05-26 15:13:01 EDT||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Timothy St. Clair 2012-08-21 11:59:05 EDT
A common use case which affects utilization is the case where the claim divy'd out to a DAG job was relinquished because DAGman had not submitted a new job in time for the it to be reused by the autocluster. This ticket is to capture the addition of +KeepClaimIdle parameter which keeps the claim alive long enough so that it can be reused by a DAG
Comment 4 Anne-Louise Tangring 2016-05-26 15:13:01 EDT
MRG-G is in maintenance only and only customer escalations will be addressed from this point forward. This issue can be re-opened if a customer escalation associated with this issue occurs.