all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Gilberto Ferreira <gilberto.nunes32@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Corosync and Cluster reboot
Date: Tue, 7 Jan 2025 11:17:15 -0300	[thread overview]
Message-ID: <CAOKSTBvSa3BN1uf5qs3X+T+PGphBjLj2E64ymHdSOBj2pPcDHw@mail.gmail.com> (raw)
In-Reply-To: <af10807d-f255-45f0-bee9-b5d0ea76619d@elettra.eu>

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)?

Well... as I said in my scenario, I just add the line token with the value
200.
I'm afraid I lack the proper knowledge to go deeper.

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?

Yes! The corosync.conf in /etc/pve will be sinc to any new server add to
the cluster, via pmxcfs.

Best regards
---


Em ter., 7 de jan. de 2025 às 11:06, Iztok Gregori <iztok.gregori@elettra.eu>
escreveu:

> 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.nunes32@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
>
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

  reply	other threads:[~2025-01-07 14:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 11:06 Iztok Gregori
2025-01-07 12:01 ` Gilberto Ferreira
2025-01-07 12:33   ` Gilberto Ferreira
2025-01-07 14:06     ` Iztok Gregori
2025-01-07 14:17       ` Gilberto Ferreira [this message]
2025-01-07 14:15     ` DERUMIER, Alexandre
2025-01-08 10:12       ` Iztok Gregori
2025-01-08 12:02         ` Alwin Antreich via pve-user
2025-01-08 12:53         ` proxmox

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=CAOKSTBvSa3BN1uf5qs3X+T+PGphBjLj2E64ymHdSOBj2pPcDHw@mail.gmail.com \
    --to=gilberto.nunes32@gmail.com \
    --cc=pve-user@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal