Bump github.com/nats-io/nats-server/v2 from 2.1.9 to 2.9.2 in /distributor

[dependabot]

Bumps github.com/nats-io/nats-server/v2 from 2.1.9 to 2.9.2.

Release notes

Sourced from github.com/nats-io/nats-server/v2's releases.

Release v2.9.2

Changelog

Go Version

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

Improved:

• Fan-out performance degraded between v2.8.4 and v2.9.0. This was mainly due to addition of message count/size accounting per-account. Some code refactoring restored or even increased the performance compared to v2.8.4 (#3504)

Fixed

• JetStream:
  • Prevent panic processing a consumer assignment. This could happen in rare situations where a stream would catchup and start processing consumer assignments while the stream itself was "stopped", for instance during a cluster-reset event following a sequence mismatch detection, etc... (#3498)
  • The FileStore implementation could have held into memory of message blocks for longer (about 5 seconds) than needed. In situations where the stream was filling up quickly, the amount of blocks held in memory could grow enough that even 5 seconds expiration could cause the memory growth to be noticeable, even more so if the garbage collection has no reason to trigger if the overall memory usage is below the host's limit (#3501)
  • Scaling a consumer down to a R=1 would work but not send a response to the CLI/application requesting that change. That is, if an application would call js.UpdateConsumer() (using the Golang client library) with a replica of 1, the call would timeout but the operation would actually succeed (#3502)
  • The consumer names paging had issues and could have returned only the API limit, which for this request is 256 (#3510)
  • Some streams may fail to be recovered if a meta-layer snapshot was done but an upstream source or mirror changed it subjects (#3508)
  • Redeliveries for consumers with the "LastPerSubject" delivery policy were not honored. Thanks to @​brentd for the report (#3511)
• Possible exit of NATS Server running as a Windows service without logging enabled when server would report invalid protocols. The workaround is to enable logging (specify a log file as opposed to have the logging directed to the Windows Event Logs). Thanks to @​BentTranberg for the report (#3497)

Complete Changes

nats-io/nats-server@v2.9.1...v2.9.2

Release v2.9.1

Changelog

Go Version

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

Added

• JetStream:
  • Ability to remove a server by peer ID instead of server name (#3473)
  • Peer ID in the meta_cluster of statsz or jsz monitoring endpoint (#3476)
  • Ability to apply a discard new policy per subject. A new JSON field in the stream configuration called discard_new_per_subject can now be set (along with discard new policy and max messages per subject > 0) (#3487)

Improved

• JetStream:
  • Optimize acknowledgment handling. Thanks to @​neilalexander for the report and contribution (#3468, #3472)

Updated

• Dependencies (#3491)

Changed

• JetStream:
  • When filtering a source stream, use the new consumer create API subject (#3478)

... (truncated)

Commits

• 6d81dde Merge pull request #3513 from nats-io/release_2_9_2
• 34851bf Release v2.9.2
• 521bfd2 Merge pull request #3512 from nats-io/update_deps
• 1039df0 [UPDATED] Dependencies
• 9cd2b7f Merge pull request #3511 from nats-io/js_last_per_subject_redeliveries
• 46aec64 [FIXED] JetStream: redeliveries for LastPerSubject delivery policy
• 0841786 Bump to 2.9.2-beta.1
• 44d4c1c Merge pull request #3508 from nats-io/meta-snap
• 91edd1a With snapshots both streams are present on restart so sources or mirrors that...
• 52b5cd1 Allow meta layer to snapshot on a clean shutdown.
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #472.