From: "Lukas Sichert" <l.sichert@proxmox.com>
To: "Michael Köppl" <m.koeppl@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH cluster/docs/manager v3 0/8] add warning messages for high token timeouts in clusters
Date: Mon, 04 May 2026 11:37:27 +0200 [thread overview]
Message-ID: <DI9SI21EUNHS.2SRT6SVTH7WJC@proxmox.com> (raw)
In-Reply-To: <20260427170548.307698-1-m.koeppl@proxmox.com>
What I have tested:
- a small selection of links using 'onlineHelp' still work
- the new link to documentation in the 'Join Information' field in the
ui using the 'get_help_link' works
-the correct messages are displayed in the cli and ui if the
`token_coefficient` is high enough
Tested-by: Lukas Sichert <l.sichert@proxmox.com>
On 2026-04-27 19:05, Michael Köppl <m.koeppl@proxmox.com> wrote:
> This patch series introduces warnings informing users about high token
> timeouts in their clusters. A recent change [0] lowered the token
> coefficient for clusters and allowed adapting it. However, this change
> only affects new clusters. As described in [1], users with existing
> cluster should be informed about the high token timeouts in their
> configurations and what they can do to alleviate this problem.
>
> Thus, warnings are added to the `pvecm status` command as well as to the
> cluster join info dialog in the web UI. The warning in the web UI warns
> users about the effect adding another node would have to allow them to
> make an informed change before adding another node.
>
> changes since v2 (thanks to @Lukas and @Friedrich for the feedback):
> - use "lowering" instead of "changing" for the warning strings
> - replace leftover hard-coded PVE docs link with `man pvecm`
> - update descriptions of timeout_warning_level and expected_timeout
> params such that they say "membership recovery timeout", to more
> clearly state which timeout this is about
> - update function names for get_timeout_warning_level and
> get_timeout_warning to
> calculate_membership_recovery_timeout_warning_level and
> calculate_membership_recovery_timeout_warning respectively
>
> changes since v1 (thanks to @Friedrich for the feedback on v1):
> - add pve-docs patch to allow using get_help_link to directly link to
> an anchor in the local documentation (then used to link to the section
> on changing the token coefficient)
> - add pve-docs patch to define explicit anchor for the "Changing the
> Token Coefficient" section
> - add pve-docs patch extending the section for Changing the Token
> Coefficient slightly, informing users of the potential warning
> messages in the pvecm status output
> - change the threshold for "strongly recommend" from 50s to 45s as
> suggested by @Friedrich
> - adapted the name of calculate_total_timeout to
> calculate_membership_recovery_timeout
> - adapted commit messages for preparatory pve-manager patch (no
> functional changes intended)
> - moved the warning message in pvecm from `pvecm nodes` to `pvecm status`
> - replaced the URL in the pvecm warning message with a reference to the
> pvecm man pages
> - link to local documentation in ClusterEdit.js
>
>
> pve-docs:
>
> Michael Köppl (3):
> asciidoc-pve: allow linking sections with get_help_link
> pvecm: add explicit anchor for token coefficient section
> pvecm: add info about warnings regarding token coefficient
>
> pvecm.adoc | 6 ++++++
> scripts/asciidoc-pve.in | 2 +-
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
>
> pve-cluster:
>
> Michael Köppl (3):
> add functions to determine warning level for high token timeouts
> pvecm: warn users of high token timeouts when using status command
> api: add token timeout and warning level to cluster join info
>
> src/PVE/API2/ClusterConfig.pm | 24 +++++++++++++++++
> src/PVE/CLI/pvecm.pm | 12 +++++++++
> src/PVE/Corosync.pm | 50 +++++++++++++++++++++++++++++++++++
> 3 files changed, 86 insertions(+)
>
>
> pve-manager:
>
> Michael Köppl (2):
> ui: cluster info: move initialization of items to initComponent
> ui: cluster info: warn users of high token timeout in join info
>
> www/manager6/dc/Cluster.js | 4 +
> www/manager6/dc/ClusterEdit.js | 141 ++++++++++++++++++++++-----------
> 2 files changed, 97 insertions(+), 48 deletions(-)
>
>
> Summary over all repositories:
> 7 files changed, 190 insertions(+), 49 deletions(-)
>
> --
> Generated by murpp 0.11.0
prev parent reply other threads:[~2026-05-04 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 17:05 [PATCH cluster/docs/manager v3 0/8] add warning messages for high token timeouts in clusters Michael Köppl
2026-04-27 17:05 ` [PATCH docs v3 1/8] asciidoc-pve: allow linking sections with get_help_link Michael Köppl
2026-04-27 17:05 ` [PATCH docs v3 2/8] pvecm: add explicit anchor for token coefficient section Michael Köppl
2026-04-27 17:05 ` [PATCH docs v3 3/8] pvecm: add info about warnings regarding token coefficient Michael Köppl
2026-04-27 17:05 ` [PATCH cluster v3 4/8] add functions to determine warning level for high token timeouts Michael Köppl
2026-04-27 17:05 ` [PATCH cluster v3 5/8] pvecm: warn users of high token timeouts when using status command Michael Köppl
2026-04-27 17:05 ` [PATCH cluster v3 6/8] api: add token timeout and warning level to cluster join info Michael Köppl
2026-04-27 17:05 ` [PATCH manager v3 7/8] ui: cluster info: move initialization of items to initComponent Michael Köppl
2026-04-27 17:05 ` [PATCH manager v3 8/8] ui: cluster info: warn users of high token timeout in join info Michael Köppl
2026-05-04 9:37 ` Lukas Sichert [this message]
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=DI9SI21EUNHS.2SRT6SVTH7WJC@proxmox.com \
--to=l.sichert@proxmox.com \
--cc=m.koeppl@proxmox.com \
--cc=pve-devel@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