From: Stefan Reiter <s.reiter@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [RFC 0/2] backup client: implement some HTTP timeouts
Date: Tue, 22 Dec 2020 09:47:17 +0100 [thread overview]
Message-ID: <dbaa42ca-791a-a8d1-8e8a-24928790aa8b@proxmox.com> (raw)
In-Reply-To: <1481561822.2144.1608568808408@webmail.proxmox.com>
On 12/21/20 5:40 PM, Dietmar Maurer wrote:
>> Came up during discussion of this report:
>> https://forum.proxmox.com/threads/qmp-command-backup-failed-got-timeout.77749/#post-357700
>>
>> where high load on the server (from too many verification tasks, which
>> is a different problem) causes VM clients to hang for unreasonable
>> amounts of time.
>
> But with a 20s timeout, the backup would fail quit fast - this is probably also not what the user wants?
>
This is only on the initial UPGRADE request, once that is established
nothing is changed. If that takes longer than 20s (or 30, 40, as stated
the exact number was more of a guess on my part) the server is probably
under enough load that another backup client isn't going to help.
next prev parent reply other threads:[~2020-12-22 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 13:56 Stefan Reiter
2020-12-21 13:56 ` [pbs-devel] [RFC proxmox 1/2] add tools::future with TimeoutFutureExt Stefan Reiter
2020-12-21 13:56 ` [pbs-devel] [RFC proxmox-backup 2/2] http_client: add timeouts for critical connects Stefan Reiter
2020-12-21 15:36 ` [pbs-devel] [RFC 0/2] backup client: implement some HTTP timeouts Dietmar Maurer
2020-12-21 15:45 ` Dietmar Maurer
2020-12-21 15:49 ` Stefan Reiter
2020-12-21 16:40 ` Dietmar Maurer
2020-12-22 8:47 ` Stefan Reiter [this message]
2020-12-22 10:40 ` Dietmar Maurer
2020-12-22 12:32 ` [pbs-devel] applied: " Dietmar Maurer
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=dbaa42ca-791a-a8d1-8e8a-24928790aa8b@proxmox.com \
--to=s.reiter@proxmox.com \
--cc=dietmar@proxmox.com \
--cc=pbs-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