Skip to content

Release v0.17.0
Compare
Choose a tag to compare
@NATS-CI NATS-CI released this 11 Feb 19:36
v0.17.0
f4b7190
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Changelog

Backward compatibility note

See backward compatibility note if moving from v0.14.3 to this release here

Go Version

  • 1.13.7: Both release executables and Docker images are built with this Go release.

Added

  • In/Out Msgs/Bytes in /serverz monitoring endpoint. Thanks to @renanberto for the report (#976)
  • server_name and skip_veriy configuration parameters (TLSServerName and TLSSkipVerify options) (#981)
  • Support for Redelivery Count. Thanks to @robertmircea, @bmcstdio, @sujeshthekkepatt, @kell18, @vtolstov and many others for their feedback (#997)
  • Ability to set log file size limit (#1018)

Updated

  • Some code cleanup. Thanks to @tegk for the contribution (#973)
  • RAFT transport timeouts, which may help reduce occurrences of error Failed to flush response: write to closed conn (#988)
  • Some dependencies, including NATS Server v2.1.4 (#1017)

Improved

  • Use NoFreelistSync for RAFT bbolt store. This was removed since v0.12.2 due to a defect in the underlying bbolt library (#989)

Fixed

  • Duplicate shadow durable queue subscription due to race. Thanks to @will-yip for the report (#951)
  • On catching SIGTERM signal, the server will now exit with error 143, which will allow kubernetes to restart the pod instead of considering it "complete". Thanks to @wanjunlei for the report and contribution (#957)
  • Typo in usage for --encryption_key. Thanks to @derekbekoe for the contribution (#978)
  • Stop subscription redelivery timer and signal handler on shutdown (#1004)
  • FileStore: Empty() should remove all message files (dat/idx) (#1011)
  • Clustering: Incorrect RAFT logging (#987)
  • Clustering: Issue with subscription "is_stalled" state on leader election that would prevent delivery of new messages. Thanks to @bfoxstudio for the report (#994)
  • Clustering: Add flag to allow node to proceed on restore failure. Thanks to @emalovan for the report (#1012)
  • Clustering: Handling of deleted channels (#1013)

Complete Changes

v0.16.2...v0.17.0

Assets 21
Loading