Distributed Replicated Block Device (DRBD) announcements
 help / color / mirror / Atom feed
From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com
Subject: drbd-reactor v1.9.0-rc.1
Date: Wed, 2 Jul 2025 12:33:09 +0200	[thread overview]
Message-ID: <aGUK5dieAg-VnTJF@arm64> (raw)

[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]

Dear DRBD users,

This is the first RC of the upcoming 1.9.0 release. It mainly contains
one new feature related to what is known as automatic switch back:

So far when preferred-nodes were set they also were taken into account
when a service was already running on a lower priority node and the
higher priority node joined later. In this case the lower priority node
stopped the local service and (most likely) the higher priority node
took over.

It is a valid use case not wanting to switch back if services are
running and a higher priority node joins. One might want to keep the
running services on the lower priority node. This is now implemented via
preferred-nodes-policy, which can be "always" (default and old
behavior) or "start-only".

If we don't find any issues we will release the final version in about a
week from now.

Regards, rck

GIT: https://github.com/LINBIT/drbd-reactor/commit/04cb730f6ba7c4d9b70f724ba1acc5ec60f936d9
TGZ: https://pkg.linbit.com//downloads/drbd/utils/drbd-reactor-1.9.0-rc.1.tar.gz
PPA: https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack

Changelog:
[ Moritz Wanzenböck ]
* ci: use git fetch instead of archive download

[ Roland Kammerer ]
* promoter: improve log message
* promoter,doc: document uname -n
* promoter: add preferred-nodes-policy

[ ggqshr ]
* Update promoter.md

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2025-07-02 10:33 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=aGUK5dieAg-VnTJF@arm64 \
    --to=roland.kammerer@linbit.com \
    --cc=drbd-announce@lists.linbit.com \
    --cc=drbd-user@lists.linbit.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