Bug 526480
| Summary: | Grid documentation should advise setting a sufficient MAX_JOBS_RUNNING for concurrent dag deployments | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Pete MacKinnon <pmackinn> |
| Component: | Documentation | Assignee: | Lana Brindley <lbrindle> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jeff Needle <jneedle> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.2 | CC: | matt, mhideo |
| Target Milestone: | 1.3 | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-09-16 16:33:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 507957 | ||
|
Description
Pete MacKinnon
2009-09-30 14:54:45 UTC
Customers and field staff should be aware that there is a current limitation in 1.2 for dagman. The schedd unfortunately does not account for the entire number of jobs running including a root dagman and its node jobs. The deferred nature of launching a dag means that the potential # of jobs is hidden until parsed by the condor_dagman process of the dag submission file. This could be exacerbated by dags that include splices and nested dags. Matt and I discussed where this type of info should be classified. Perhaps not the User Guide but maybe in a Planning section for an Admin guide? Knocking this back to the "documentation" (generic) component until we decide where to put it. LKB Note, in 7.4, MAX_JOBS_RUNNING is now an expression and independent of a START_SCHEDULER_UNIVERSE expression. Can someone please advise if this change is relevant to 1.3, and if so, where the information needs to be included. Thanks, Lana We are trying to get a KB article written for this. Awaiting feedback from Mike Cressman or Jon Thomas (or someone with KB experience). Any pointers? GSS is in charge of KB, but I have it on good authority that ECS can create articles if we need to. They remain internal until they're approved by GSS. The problem with that is I'm on leave until 7 June. If you want it done earlier than that, you might be better off contacting dpowles directly. LKB KB article http://kbase.redhat.com/faq/docs/DOC-33345 submitted to SME jthomas for tech review |