From: "Mark Schouten" <mark@tuxis.nl>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>,
"Proxmox Backup Server development discussion"
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Scheduler causing connectivity issues?
Date: Wed, 13 Jul 2022 10:41:07 +0000 [thread overview]
Message-ID: <em6ccc3570-c17d-4163-8fab-8d65148acc39@e231eb23.com> (raw)
In-Reply-To: <3283c4b8-7df3-8cd8-2886-b6d14ee3633b@proxmox.com>
Requested files sent offlist.
—
Mark Schouten, CTO
Tuxis B.V.
mark@tuxis.nl
------ Original Message ------
From "Thomas Lamprecht" <t.lamprecht@proxmox.com>
To "Mark Schouten" <mark@tuxis.nl>; "Proxmox Backup Server development
discussion" <pbs-devel@lists.proxmox.com>
Date 13/07/2022 10:14:07
Subject Re: [pbs-devel] Scheduler causing connectivity issues?
>Hi,
>
>Am 11/07/2022 um 10:44 schrieb Mark Schouten:
>>>>Hope you guys can find something.. If I need to debug anything, let me know!
>>>
>>>Thanks for the info, this already helps quite a bit. We'll look into it and re-check
>>>with you if we need more info.
>>>
>>
>>Any chance you can think of a workaround for the time being, other than downgrading?
>
>
>We identified a few places where blocking operations (e.g., the list snapshots API
>endpoint) that may starve the network request accept loop in some realistic scenarios,
>we'll move those out to their own separate thread to avoid such blockage.
>
>FWIW, it would be still interesting to see a few metrics/CLI outputs from an affected
>system to hopefully ensure that there's nothing additional to that problem.
>
>- `head /proc/pressure/*` for some general info if the system is overloaded
>- `ls /var/lib/proxmox-backup/jobstates` just out of interest
>- `ss -tlpn` to see if another (old) proxy process is still accepting
>- `uptime`
>
>
>
next prev parent reply other threads:[~2022-07-13 10:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 15:49 Mark Schouten
2022-07-08 7:09 ` Thomas Lamprecht
2022-07-08 9:36 ` Jorge Boncompte
2022-07-08 9:40 ` dea
2022-07-11 8:44 ` Mark Schouten
2022-07-13 7:55 ` dea
2022-07-13 8:14 ` Thomas Lamprecht
2022-07-13 10:41 ` Mark Schouten [this message]
2022-07-15 11:49 ` Thomas Lamprecht
2022-07-15 12:01 ` dea
2022-07-15 12:57 ` Thomas Lamprecht
2022-07-15 13:02 ` dea
2022-07-15 13:24 ` dea
2022-07-15 14:43 ` dea
2022-07-17 15:04 ` dea
2022-07-18 13:30 ` Thomas Lamprecht
2022-07-19 11:01 ` David Lawley
2022-07-19 13:04 ` Thomas Lamprecht
2022-07-19 15:08 ` dea
2022-07-18 7:31 ` Mark Schouten
2022-07-18 11:03 ` Thomas Lamprecht
2022-07-20 7:30 ` Mark Schouten
2022-07-21 13:10 ` Thomas Lamprecht
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=em6ccc3570-c17d-4163-8fab-8d65148acc39@e231eb23.com \
--to=mark@tuxis.nl \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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