Mailing List ArchivesPublic Access |
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesPublic Access |
|
|
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.
-tj From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx]
On Behalf Of Jason Liu Hi, 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? Cheers Jason PRIVACY AND CONFIDENTIALITY NOTICE |