Bug 474186
Summary: | Additional FAQ on HA Schedd issue | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | William Henry <whenry> |
Component: | Grid_User_Guide | Assignee: | Lana Brindley <lbrindle> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jeff Needle <jneedle> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.1 | CC: | mhideo |
Target Milestone: | 1.1.1 | Keywords: | Documentation |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-12-05 06:13:27 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: |
Description
William Henry
2008-12-02 17:45:57 UTC
<qandaentry> <question> <para> I have a High Availability setup, but sometimes the <command>scheddd</command> keeps on trying to start but exits with a <parameter>status 0</parameter>. Why is this happening? </para> </question> <answer> <para> In an High-Available Scheduler setup with 2 nodes (Node A and Node B), Condor will start on Node A and brings up the <command>schedd</command>, before it starts on Node B. On node B, the <command>schedd</command> continually attempts to start and exits with <parameter>status 0</parameter>. </para> <para> This can be caused by the two nodes using different HA <command>schedd</command> names. In this case, the <command>schedd</command> on Node B will continually try to start, but will not be able to because of lock conflicts. </para> <para> This problem can be solved by using the same name for the <command>schedd</command> on both nodes. This will make the <command>schedd</command> on Node B realize that one is already running, and it doesn't need to start. Change the <command>SCHEDD_NAME</command> configuration entry on both nodes so that the name is identical. </para> <para> Note that this configuration will allow other schedulers to run on other nodes besides the HA <command>SCHEDD_NAME</command>. So you can have HA (on two nodes) and other <command>schedd</command>s elsewhere. </para> </answer> </qandaentry> LKB |