Bug 477210 - shadowd: more proactive about reconnecting to a restarted startd listening on a new port
shadowd: more proactive about reconnecting to a restarted startd listening on...
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor (Show other bugs)
x86_64 Linux
low Severity medium
: 2.1.1
: ---
Assigned To: Timothy St. Clair
MRG Quality Engineering
Depends On:
  Show dependency treegraph
Reported: 2008-12-19 12:09 EST by Pete MacKinnon
Modified: 2011-12-08 14:59 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-11-03 16:56:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pete MacKinnon 2008-12-19 12:09:08 EST
Description of problem:
Currently a shadowd with jobs that has become disconnected from a startd that is listening on a new port tries in vain to reconnect on the old startd port. The lease will eventually expire and shadowd will go back through a full reconnection sequence and the shadow jobs will be re-started successfully. This process could be expedited if the shadowd after a configured amount of time or failed reconnect attempts tries to get the new port from some config lookup (i.e., before the lease expires).

Version-Release number of selected component (if applicable):
$CondorVersion: 7.2.0 Dec 16 2008 BuildID: RH-7.2.0-0.13.el5 PRE-RELEASE-UWCS $
$CondorPlatform: X86_64-LINUX_RHEL5 $

How reproducible:
Should be 100%

Steps to Reproduce:
1. Start personal condor as service
2. Submit 30 sleep jobs
3. Note normal slot/job dispatch behavior in steady state
4. Restart condor services
5. Run condor_q and note jobs are in R
6. Run condor_status and note all slots are available and idle
Actual results:
After a condor restart, condor_q reports jobs in R state but condor_status says slots are Unclaimed. The ShadowLog reports the re-connection attempts and failures.

Expected results:
The queued jobs should be run after a condor restart assuming slots are available.

Additional info:
Couldn't this just be achieved by tweaking the lease expiry time?
Comment 1 Matthew Farrellee 2010-02-05 16:07:59 EST
A workaround may be to use STARTD_ARGS = -p 1234 and have the Startd always come up on the same port.
Comment 3 Timothy St. Clair 2011-11-02 17:33:48 EDT
Does this issue even exist any more if one uses shared_port?
Comment 4 Pete MacKinnon 2011-11-02 17:41:41 EDT
Perhaps not.
Comment 5 Timothy St. Clair 2011-11-03 16:56:38 EDT
I can not repro the above according to the instructions (default using shared port).

Note You need to log in before you can comment on or make changes to this bug.