On 07/01/25 13:33, Gilberto Ferreira wrote:
Just to clarify, I had a similar issue in a low latency network with 12
nodes cluster, all with 1G ethernet card.
After adding this token_retransmit to corosync.conf, no more problems.
Perhaps that could help you.
Em ter., 7 de jan. de 2025 às 09:01, Gilberto Ferreira <
gilberto.nune...@gmail.com> escreveu:
Try to add this in corosync.conf in one of the nodes: token_retransmit:
200
Hi and thank you for your suggestion!
Right now this is the configuration of the token in our cluster:
root@aaa:~# corosync-cmapctl | grep token
runtime.config.totem.token (u32) = 12750
runtime.config.totem.token_retransmit (u32) = 3035
runtime.config.totem.token_retransmits_before_loss_const (u32) = 4
The token_retransmit is calculated automatically by the formula
token / (token_retransmits_before_loss_const + 0.2)
and in our case is 3035 miliseconds. I have 2 questions:
1. Because the value is automatically calculated is better to increase
the value "retransmits_before_loss_const" (or decrease the "token"
value) than to set a constant (200 milliseconds for example)?
2. If I alter this value and in the future a node will be added/removed,
the value will remain the same or it will be recalculated?
Thanks
Iztok
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
