Hello.
I have a 4-node cluster. Some of them have been updated to version 5.1. I noticed the following messages in the log:
Nov 27 11:18:47 pve0 corosync[6600]: [TOTEM ] Retransmit List: 85cc
Nov 27 11:18:47 pve0 corosync[6600]: [TOTEM ] Retransmit List: 85cc
Nov 27 11:19:17 pve0 corosync[6600]: [TOTEM ] Retransmit List: 8672 8673
Nov 27 11:19:28 pve0 corosync[6600]: [TOTEM ] Retransmit List: 86b1
...
corosync.conf
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: pve1
nodeid: 2
quorum_votes: 1
ring0_addr: pve1
}
node {
name: pve2
nodeid: 3
quorum_votes: 1
ring0_addr: pve2
}
node {
name: pve4
nodeid: 5
quorum_votes: 1
ring0_addr: pve4
}
node {
name: pve3
nodeid: 4
quorum_votes: 1
ring0_addr: pve3
}
node {
name: pve0
nodeid: 1
quorum_votes: 1
ring0_addr: pve0
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: www-klass
config_version: 7
ip_version: ipv4
secauth: on
version: 2
interface {
bindnetaddr: 192.168.10.253
ringnumber: 0
}
}
Quorum information
------------------
Date: Mon Nov 27 11:28:42 2017
Quorum provider: corosync_votequorum
Nodes: 5
Node ID: 0x00000001
Ring ID: 5/1028
Quorate: Yes
Votequorum information
----------------------
Expected votes: 5
Highest expected: 5
Total votes: 5
Quorum: 3
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000005 1 192.168.10.250
0x00000004 1 192.168.10.251
0x00000003 1 192.168.10.252
0x00000001 1 192.168.10.253 (local)
0x00000002 1 192.168.10.254
This problem can be due to the fact that some nodes of version 4.x, some 5.1?
I have a 4-node cluster. Some of them have been updated to version 5.1. I noticed the following messages in the log:
Nov 27 11:18:47 pve0 corosync[6600]: [TOTEM ] Retransmit List: 85cc
Nov 27 11:18:47 pve0 corosync[6600]: [TOTEM ] Retransmit List: 85cc
Nov 27 11:19:17 pve0 corosync[6600]: [TOTEM ] Retransmit List: 8672 8673
Nov 27 11:19:28 pve0 corosync[6600]: [TOTEM ] Retransmit List: 86b1
...
corosync.conf
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: pve1
nodeid: 2
quorum_votes: 1
ring0_addr: pve1
}
node {
name: pve2
nodeid: 3
quorum_votes: 1
ring0_addr: pve2
}
node {
name: pve4
nodeid: 5
quorum_votes: 1
ring0_addr: pve4
}
node {
name: pve3
nodeid: 4
quorum_votes: 1
ring0_addr: pve3
}
node {
name: pve0
nodeid: 1
quorum_votes: 1
ring0_addr: pve0
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: www-klass
config_version: 7
ip_version: ipv4
secauth: on
version: 2
interface {
bindnetaddr: 192.168.10.253
ringnumber: 0
}
}
Quorum information
------------------
Date: Mon Nov 27 11:28:42 2017
Quorum provider: corosync_votequorum
Nodes: 5
Node ID: 0x00000001
Ring ID: 5/1028
Quorate: Yes
Votequorum information
----------------------
Expected votes: 5
Highest expected: 5
Total votes: 5
Quorum: 3
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000005 1 192.168.10.250
0x00000004 1 192.168.10.251
0x00000003 1 192.168.10.252
0x00000001 1 192.168.10.253 (local)
0x00000002 1 192.168.10.254
This problem can be due to the fact that some nodes of version 4.x, some 5.1?