* [PVE-User] Migration target node in case of shutdown @ 2022-04-14 9:36 Maximilian Hill 2022-04-14 10:40 ` Stefan Sterz 0 siblings, 1 reply; 3+ messages in thread From: Maximilian Hill @ 2022-04-14 9:36 UTC (permalink / raw) To: pve-user [-- Attachment #1: Type: text/plain, Size: 115 bytes --] Hello, how exactly does Proxmox VE determine the target node of a migration in case of a shutdown? Thanks, Max [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PVE-User] Migration target node in case of shutdown 2022-04-14 9:36 [PVE-User] Migration target node in case of shutdown Maximilian Hill @ 2022-04-14 10:40 ` Stefan Sterz 2022-04-14 10:50 ` Maximilian Hill 0 siblings, 1 reply; 3+ messages in thread From: Stefan Sterz @ 2022-04-14 10:40 UTC (permalink / raw) To: Proxmox VE user list, Maximilian Hill Hello, the target node is chosen by the node priority of the HA group that a VM is in. You can read more about that in the manual [1]. Here is an example: Assuming you have a three node cluster (node0, node1, node2) and the HA group has the following priorities: node0:2, node1:1, node2:0. A VM running on node0 will be moved to node1 and then node2 if each node fails one after another. If several nodes have the same priority, VMs will be distributed evenly. Best regards, Stefan [1]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#ha_manager_groups On 14.04.22 11:36, Maximilian Hill wrote: > Hello, > > how exactly does Proxmox VE determine the target node of a migration in > case of a shutdown? > > > Thanks, > > Max > > > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PVE-User] Migration target node in case of shutdown 2022-04-14 10:40 ` Stefan Sterz @ 2022-04-14 10:50 ` Maximilian Hill 0 siblings, 0 replies; 3+ messages in thread From: Maximilian Hill @ 2022-04-14 10:50 UTC (permalink / raw) To: Stefan Sterz; +Cc: Proxmox VE user list [-- Attachment #1: Type: text/plain, Size: 1317 bytes --] Hello Stefan, the reason I'm asking, is, that I ran into a case, in which the priorities were all equal (not set), but all VMs were tried to migrate from two nodes to the same node of a 8 node cluster. This by itself wouldn't really be a problem, but qemu managed to allocate all the memory for the VMs, so no migration failed to start. Then the VMs used the memory and the OOM started to kill VMs and other processes. In this special case, we have a temporary workaround in place: - No swap - vm.overcommit_memory = 2 - vm.overcommit_ratio = 99 This of course is not a nice solution at all. Best regards, Max On Thu, Apr 14, 2022 at 12:40:35PM +0200, Stefan Sterz wrote: > Hello, > > the target node is chosen by the node priority of the HA group that a > VM is in. You can read more about that in the manual [1]. Here is an > example: Assuming you have a three node cluster (node0, node1, node2) > and the HA group has the following priorities: node0:2, node1:1, > node2:0. A VM running on node0 will be moved to node1 and then node2 > if each node fails one after another. If several nodes have the same > priority, VMs will be distributed evenly. > > Best regards, > Stefan > > [1]: > https://pve.proxmox.com/pve-docs/pve-admin-guide.html#ha_manager_groups > > [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-04-14 11:05 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-04-14 9:36 [PVE-User] Migration target node in case of shutdown Maximilian Hill 2022-04-14 10:40 ` Stefan Sterz 2022-04-14 10:50 ` Maximilian Hill
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox