DHCP is fine,Â actually *changing* the IP assigned to a HTCondor node without also restarting HTCondor on that node will not work.
A lot of DHCP configurations will tie IP assignments to MAC addresses, so that while IPs can change in theory, in practice they almost never actually change unless the hardware also changes, in which case a restart of HTCondor would end up happening also.ÂÂ With this sort of DHCP configuration, HTCondor works just fine.
But if you really do randomly change IP assignments every few days, then HTCondor will not work well. ÂÂThe problem is that HTCondor daemons normally push their network address into the collector in the form of their current preferred IP address.Â And they figure THAT out at process start.Â So a change of IP without a restart of the Daemons will result in the various daemons not knowing how to talk to each other over time.
There is no configuration change to make this work better.
We have a cluster where host IPs are dynamic, assigned by DHCP. But all host names are static.
Would HTCondor work on such a cluster? Specifically what happens to HTCondor during a DHCP renew?
Is there anything I need set in the condor_config file to allow it to work?
PRIVACY AND CONFIDENTIALITY NOTICE
The information contained in this message is intended for the named recipients only. It may contain confidential information and if you are not the intended recipient, you must not copy, distribute or take any action in reliance on it. If you have received this message in error please destroy it and reply to the sender immediately or contact us at the above telephone number.
While we take every precaution against presence of computer viruses on our system, we accept no responsibility for loss or damage arising from the transmission of viruses to e-mail recipients.
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: