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

[dependabot]

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

Release notes

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

Release v2.9.3

Changelog

Go Version

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

Fixed

• JetStream:
  • Unresponsiveness (health check failures, routes being blocked) while creating a RAFT group when disk performance if very slow. Thanks to @​TomasVojacek for the report (#3519)
  • Purge with additional options may leave some messages in the stream (#3529)
  • Prevent stack overflow when an account imports its own export. CVE-2022-42709 (#3538)
  • Prevent panic on negative replicas count. CVE-2022-42708 (#3539)
  • User-provided ephemeral consumer name was not used in cluster mode, that is, the server would still pick a random name (#3537)
• Added missing command line options in the -help section. Thanks to @​ariel-zilber for the contributions (#3523, #3527)

Complete Changes

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

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 1024 (#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

... (truncated)

Commits

• 25e82d7 Merge pull request #3542 from nats-io/release_2_9_3
• 096b822 Release v2.9.3
• 09b9bf2 Merge pull request #3541 from nats-io/warn_slow_icb
• 3358247 Added warning if internal sub callback takes too long
• ffc1797 Merge pull request #3537 from nats-io/js_cons_name
• 9bd1158 [FIXED] JetStream: User-defined ephemeral Name not used in cluster mode
• e42260c Merge pull request #3539 from nats-io/js_handle_bad_replicas_count
• cf71adb Merge pull request #3538 from nats-io/fix_import_own_export
• c3adf78 [FIXED] Stack overflow when account imports its own export
• 3c7aa55 [FIXED] JetStream: return error on negative replicas count
• 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 #485.