From: Maximilian Hill <mhill@inett.de>
To: Stefan Sterz <s.sterz@proxmox.com>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Migration target node in case of shutdown
Date: Thu, 14 Apr 2022 12:50:09 +0200 [thread overview]
Message-ID: <Ylf8YVinPVea29vw@inett.de> (raw)
In-Reply-To: <342bf09c-3113-eddf-1950-6dba41e4b771@proxmox.com>
[-- 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 --]
prev parent reply other threads:[~2022-04-14 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 9:36 Maximilian Hill
2022-04-14 10:40 ` Stefan Sterz
2022-04-14 10:50 ` Maximilian Hill [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Ylf8YVinPVea29vw@inett.de \
--to=mhill@inett.de \
--cc=pve-user@lists.proxmox.com \
--cc=s.sterz@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox