Description of problem: Provide documentation of, and usage for, the GROUP_DYNAMIC_MACH_CONSTRAINT parameter. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
When the Hierarchical Fair Share (HFS) algorithm computes the number of slots it will give to each accounting group, it may include slots that cannot accept any matches during the subsequent negotiation. This may cause the first groups that negotiate to receive a disproportionate number of the actual matchable slots, and subvert the intention of HFS. The condor administrator may choose to mitigate this behavior by setting the GROUP_DYNAMIC_MACH_CONSTRAINT configuration parameter. GROUP_DYNAMIC_MACH_CONSTRAINT stores a boolean expression which is evaluated for each candidate slot. Slots for which this expression evaluates to True are considered by HFS. For example, one useful setting to focus HFS on matchable slots would be: GROUP_DYNAMIC_MACH_CONSTRAINT = (State != "Owner") && (Cpus > 0) This setting causes HFS to consider slots on machines which are currently unused, and which have CPUs to allocate. Another example is: GROUP_DYNAMIC_MACH_CONSTRAINT = (State == "Unclaimed") Which causes HFS to consider only unclaimed slots.
*** This bug has been marked as a duplicate of bug 639358 ***