NATS - v2.7.3
Changelog
Go Version
- 1.17.7: Both release executables and Docker images are built with this Go release.
Added
- JetStream:
- Allow replica updates during stream update (#2867)
- Allow stream placement by tags (#2871)
Updated
- Dependencies:
github.com/klauspost/compress
: v1.13.4 -> v1.14.4github.com/minio/highwayhash
: v1.0.1 -> v1.0.2
Improved
- JetStream:
- Sparse consumers replay time. This is when a stream has multiple subjects and a consumer filters the stream to a small and spread out list of messages (#2848, #2863)
- Small improvements to send performance when sending to a full stream (#2877)
Fixed
- Gateway:
- Connection could fail with 'Authorization Violation' and parser error due to an initial
PING
possibly sent prior to theCONNECT
protocol. Also, the server accepting a connection was not starting the authentication timer, which responsibility is to close the connection if theCONNECT
protocol is not received within the gateway's authentication timeout. It can be configured withauthorization{ timeout: 5.0 }
in thegateway{}
block, but if not set will default to 2 seconds. Thanks to @jimenj1970 for the report (#2881)
- Connection could fail with 'Authorization Violation' and parser error due to an initial
- JetStream:
- Flow control stall under specific conditions of messages size (#2847)
- A stream name is tied to its identity and cannot be changed on restore (#2857)
- The consumer information's state in response to a consumer create request could return inaccurate information, specially regarding number of pending messages (#2858)
- Remove "fss" files from a snapshot when a block is removed. Thanks to @nekufa for the report (#2859)
- Prevent a panic when stream restore fails (#2864
- Interest policy and staggered filtered consumers could fail to remove messages. Thanks to @lukasGemela for the report (#2875)
- Remove "key" files when removing message blocks and encryption is used. Thanks to @exename for the report (#2878)
- Reduce logging for internal message exchange (#2879)
- Rare possible re-use of internal RAFT inbox that could cause a node to receive a message on the wrong inbox, possibly leading to a panic. Servers would likely have to be started at the exact same time for that to happen (#2879)
Complete Changes
https://github.com/nats-io/nats-server/compare/v2.7.2...v2.7.3
Details
date
Feb. 24, 2022, 9:29 p.m.
name
Release v2.7.3
type
Patch
👇
Register or login to:
- 🔍View and search all NATS releases.
- 🛠️Create and share lists to track your tools.
- 🚨Setup notifications for major, security, feature or patch updates.
- 🚀Much more coming soon!