> I wonder if something like pacemaker sbd could be implemented in proxmox as > extra layer of protection ?
>>AFAIK Thomas already has patches to implement active fencing. >>But IMHO this will not solve the corosync problems.. Yes, sure. I'm really to have to 2 differents sources of verification, with different path/software, to avoid this kind of bug. (shit happens, murphy law ;) as we say in French "ceinture & bretelles" -> "belt and braces" BTW, a user have reported new corosync problem here: https://forum.proxmox.com/threads/proxmox-6-2-corosync-3-rare-and-spontaneous-disruptive-udp-5405-storm-flood.75871 (Sound like the bug that I have 6month ago, with corosync bug flooding a lof of udp packets, but not the same bug I have here) ----- Mail original ----- De: "dietmar" <diet...@proxmox.com> À: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>, "aderumier" <aderum...@odiso.com>, "Thomas Lamprecht" <t.lampre...@proxmox.com> Envoyé: Lundi 14 Septembre 2020 09:14:50 Objet: Re: [pve-devel] corosync bug: cluster break after 1 node clean shutdown > I wonder if something like pacemaker sbd could be implemented in proxmox as > extra layer of protection ? AFAIK Thomas already has patches to implement active fencing. But IMHO this will not solve the corosync problems.. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
