From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-announce@lists.linbit.com
Cc: drbd-user@lists.linbit.com
Subject: [DRBD-announce] drbd-9.1.18-rc.1 and drbd-9.2.7-rc.1
Date: Wed, 13 Dec 2023 21:42:18 +0100 [thread overview]
Message-ID: <86r0jphm1h.fsf@linbit.com> (raw)
Hello,
Here comes the DRBD December release. drbd-9.1.18-rc.1 and drbd-9.2.7-rc.1.
We have two updates that are worth mentioning.
One, the RDMA transport finally reaches general usability. As usual, I
have plans to improve it further, it never stops.
The other improvement is in the area of the quorum code. For a cluster
containing two nodes with backing disks and a diskless tiebreaker node,
our quorum implementation can preserve quorum on a single storage node
with the help of the tiebreaker node.
Up to now, it has lost quorum when that remaining storage node restarts.
Now we are improving that, it will restore quorum from the meta-data in
case it reboots.
Please help test the release candidates.
9.2.7-rc.1 (api:genl2/proto:86-122/transport:19)
--------
* Fixed wrong tx-timeouts in the RDMA transport
* Recreate buffers promptly for the RDMA transport, improving
performance a lot
* changes merged from drbd-9.1.18
- Fixed connecting nodes with differently sized backing disks,
specifically when the smaller node is primary, before establishing
the connections
- Fixed thawing a device that has I/O frozen after loss of quorum
when a configuration change eases its quorum requirements
- Properly fail TLS if requested (only available in drbd-9.2)
- Fixed a race condition that can cause auto-demote to trigger right
after an explicit promote
- Preserve "tiebreaker quorum" over a reboot of the last node (3-node
clusters only)
- Update compatibility code for Linux 6.6
https://pkg.linbit.com//downloads/drbd/9/drbd-9.2.7-rc.1.tar.gz
https://github.com/LINBIT/drbd/commit/7f22671f5e852604d0383c499b96e1c2fe87901c
https://pkg.linbit.com//downloads/drbd/9/drbd-9.1.18-rc.1.tar.gz
https://github.com/LINBIT/drbd/commit/aaba2a8236b623538aa1c54b46b8ea48c782a03b
cheers,
Phil
reply other threads:[~2023-12-13 20:42 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=86r0jphm1h.fsf@linbit.com \
--to=philipp.reisner@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