public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lucas Barros <lucasbarros.kam@gmail.com>
Subject: applied: [PATCH ha-manager] fix #8240: lrm: keep try count when re-queuing a waiting command
Date: Wed, 11 Nov 2026 23:55:56 +0100	[thread overview]
Message-ID: <179443775015.1700639.5110568834727775975.b4-ty@b4> (raw)
In-Reply-To: <20261111215805.8414-1-lucasbarros.kam@gmail.com>

On Wed, 11 Nov 2026 18:58:05 -0300, Lucas Barros wrote:
> Commit 65c1fba ("lrm: avoid job starvation on huge workloads") made
> run_workers() prefer queued commands that were already passed over
> more often, so that every resource gets its turn eventually when not
> all queued commands can be started within one LRM round.
> 
> But manage_resources() queues the current command of every resource
> again in each round, and queue_resource_command() replaces a queued,
> not yet started command with a fresh entry with 'start_tries' reset to
> 0. So at the start of every round all waiting commands are equal again
> and the sort falls back to the service ID: with more resources than
> the LRM can handle in one round, the lexicographically first ones are
> checked every round, while the others are never started and stay in
> their state, e.g. 'starting', for as long as the load lasts.
> 
> [...]

Applied, thanks!

[1/1] fix #8240: lrm: keep try count when re-queuing a waiting command
      commit: 2dce90fc635fb91cae11ccdb535140589b74323c




      reply	other threads:[~2026-11-11 22:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 21:58 [PATCH ha-manager] fix #8240: lrm: keep try count when re-queuing a waiting command Lucas Barros
2026-11-11 22:55 ` Thomas Lamprecht [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=179443775015.1700639.5110568834727775975.b4-ty@b4 \
    --to=t.lamprecht@proxmox.com \
    --cc=lucasbarros.kam@gmail.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal