Proxmox VE 4.0 beta1 released!

Status
Not open for further replies.

wolfgang

Proxmox Staff Member
Staff member
Oct 1, 2014
4,763
316
83
All new Mainboards have hardware watchdogs so there is normally no need for extra device. If not softdog is a part of the kernel and works.
 

amartin

New Member
Jun 25, 2015
5
0
1
All new Mainboards have hardware watchdogs so there is normally no need for extra device. If not softdog is a part of the kernel and works.
Would the hardware watchdog work in conjunction with shared storage fencing, e.g how Pacemaker uses sbd?

In any of these cases, how do the other nodes know for certain that the rogue node has been killed? Do they simply wait for the watchdog timer period and then after that assume that the node has been killed?
 

wolfgang

Proxmox Staff Member
Staff member
Oct 1, 2014
4,763
316
83
It doesn't matter if the the node is not reachable from the cluster or off.
consider if the rest cluster has quorum then the cluster know everything is ok and the one node what is missing is not ok.
so after a time widows (dependence on different thinks) the cluster will believe the node is down (self fencing).
if no one has quorum it doesn't matter how the real state is, there are no node how can make decision.
 

amartin

New Member
Jun 25, 2015
5
0
1
We use a distributed locking mechanism, combined with the watchdog feature.
wolfgang said:
It doesn't matter if the the node is not reachable from the cluster or off.
consider if the rest cluster has quorum then the cluster know everything is ok and the one node what is missing is not ok.

The concern I have is if the rogue node were to "recover" from the failed state and then start writing bad data to the shared storage (e.g DRBD, ceph, NFS, etc) at the same time as the new node that took over its VMs. If this were to occur, wouldn't it result in two nodes writing data to the same VM image files at once and thus corrupting them?
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
16,484
315
83
Austria
www.proxmox.com
[/COLOR]The concern I have is if the rogue node were to "recover" from the failed state and then start writing bad data to the shared storage (e.g DRBD, ceph, NFS, etc) at the same time as the new node that took over its VMs. If this were to occur, wouldn't it result in two nodes writing data to the same VM image files at once and thus corrupting them?
Our software solves exactly that problem. Or what do you think the software is for?
 

amartin

New Member
Jun 25, 2015
5
0
1
Our software solves exactly that problem. Or what do you think the software is for?
The mechanism that it uses to solve that problem is generic in that it can work with any shared storage backend (DRBD, NFS, Ceph, Gluster, iSCSI, etc)? Does it intercept I/O requests to the shared storage or how does it work?
 

haxxa

New Member
Jun 26, 2015
29
1
3
Is it still recommended to use a 32bit OS in an LXC container in terms of resources?
 

sengo

New Member
Feb 19, 2009
27
0
1
I see in the docs that the minimum number of nodes for an ha confiuration is 3. Is a 2 node cluster no longer supported?
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
13,643
420
83

sengo

New Member
Feb 19, 2009
27
0
1
What a pity. Two node cluster are the most common configuration for us...
 

sengo

New Member
Feb 19, 2009
27
0
1
Not recommended is a thing. Unsupported and impossible to enable is another...
 

wolfgang

Proxmox Staff Member
Staff member
Oct 1, 2014
4,763
316
83
How I wrote before Corosync has no quorumdisk anymore. That the point.
And it is not impossible but not reliable. Or where is the decision breaker when you have a 2 node cluster split?
 
Last edited:

sengo

New Member
Feb 19, 2009
27
0
1
Do you mean using:quorum {provider: corosync_votequorumtwo_node: 1}I'm no cluster expert, but how does other softwares deal with 2 node clusters (eg VMware) without fencing and quorum disks?
 
Status
Not open for further replies.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!