The nodes can be upgraded in any order. However, since 8.8.15 is a security release that addresses problems in the collector and schedd, it would be wise to upgrade your Central Manager and Submit nodes first. As stated earlier, upgrading these nodes should
have little effect on jobs.
Depending on what you want to accomplish: 1) you can upgrade your execute nodes and running jobs on that node will be interrupted and started on another node, or 2) you could drain an execute node of jobs and then upgrade it.
--
Tim Theisen (he, him, his) Release Manager HTCondor & Open Science Grid Center for High Throughput Computing Department of Computer Sciences University of Wisconsin - Madison 4261 Computer Sciences and Statistics 1210 W Dayton St Madison, WI 53706-1685 +1 608 265 5736 From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Todd L Miller <tlmiller@xxxxxxxxxxx>
Sent: Wednesday, September 15, 2021 8:58 AM To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx> Subject: Re: [HTCondor-users] how to upgrade producing less damage as possible > * in which order the nodes should be upgraded?
I'll let the actual sysadmins on this list answer this question. > * 8.8.12 and 8.8.15 nodes can coexist? Yes. > * If I stop the central manager or the submitter, running jobs will be broke? Stopping the central manager will have no effect on running jobs. It will prevent new jobs from starting until it comes back up. Stopping the submit node will not kill jobs if you have job leases turned on (they are by default, IIRC) and the schedd comes up before the lease expires. - ToddM _______________________________________________ HTCondor-users mailing list To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a subject: Unsubscribe You can also unsubscribe by visiting https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users The archives can be found at: https://lists.cs.wisc.edu/archive/htcondor-users/ |