From: Marco Gaiarin <gaio@lilliput.linux.it>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Relax corosync timeout...
Date: Wed, 11 Jan 2023 09:16:40 +0100 [thread overview]
Message-ID: <6s729j-uk8.ln1@hermione.lilliput.linux.it> (raw)
In a 3 node PVE cluster i was forced, for now, to use a shared network for
data and sync.
When there's a traffic peak, i got:
Jan 10 23:35:09 svpve3 corosync[2884]: [KNET ] link: host: 1 link: 0 is down
Jan 10 23:35:09 svpve3 corosync[2884]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Jan 10 23:35:09 svpve3 corosync[2884]: [KNET ] host: host: 1 has no active links
Jan 10 23:35:11 svpve3 corosync[2884]: [KNET ] rx: host: 1 link: 0 is up
Jan 10 23:35:11 svpve3 corosync[2884]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Jan 10 23:35:19 svpve3 corosync[2884]: [KNET ] link: host: 1 link: 0 is down
Jan 10 23:35:19 svpve3 corosync[2884]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Jan 10 23:35:19 svpve3 corosync[2884]: [KNET ] host: host: 1 has no active links
Jan 10 23:35:21 svpve3 corosync[2884]: [KNET ] rx: host: 1 link: 0 is up
Jan 10 23:35:21 svpve3 corosync[2884]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Jan 10 23:35:45 svpve3 corosync[2884]: [TOTEM ] Token has not been received in 2737 ms
Jan 10 23:35:46 svpve3 corosync[2884]: [TOTEM ] A processor failed, forming new configuration: token timed out (3650ms), waiting 4380ms for consensus.
Jan 10 23:35:48 svpve3 corosync[2884]: [QUORUM] Sync members[3]: 1 2 3
Jan 10 23:35:48 svpve3 corosync[2884]: [TOTEM ] A new membership (1.2fd) was formed. Members
I've looked at 'man corosync.conf' but is not clear to me if and what
parameter i can modify to have corosync prevent emit this warning too much.
Thanks.
--
Errare è umano, ma per fare veramente casino
ci vuole la password di root (Zio Budda)
reply other threads:[~2023-01-11 12:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6s729j-uk8.ln1@hermione.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox