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

[dependabot]

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

Release notes

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

Release v2.9.5

Changelog

Go Version

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

Fixed

• JetStream:
  • Honor MaxMsgsPerSubject on stream update (#3595)
  • Errors such as "wrong sequence for skipped msg" or "expected sequence does not match store " while processing snapshots of streams with expired messages. Thanks to @​MauriceVanVeen and @​sylrfor the reports (#3589, #3596)
• Sublist's cache hit rate would be wrong in presence of multiple accounts. Thanks to @​aopetrov86 for the report and contribution (#3591)

Complete Changes

nats-io/nats-server@v2.9.4...v2.9.5

Release v2.9.4

Changelog

Go Version

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

Fixed

• Configuration Reload:
  • The option allow_non_tls would be ignored after a configuration reload. Thanks to @​JulienVdG for the report (#3583)
• JetStream:
  • Possible deadlock. Thanks to @​ashumkin for the report and @​neilalexander for the contribution (#3555)
  • Possible panic in disk full situations. Thanks to @​fantashley for the contribution (#3560, #3568)
  • "First sequence mismatch" after a restart/deployment with streams that have message TTLs. Thanks to @​MauriceVanVeen for the report (#3567)
  • Update of an R1 consumer would not get a response. The update was accepted by the server, but the client library or NATS CLI would timeout waiting for the response (#3574)
  • Update of a consumer's InactiveThreshold would not always take effect. Thanks to @​neilalexander for the contribution (#3575)
  • A consumer may not be removed based on InactiveThreshold in presence of gateways (#3575)
  • Migration of ephemerals on server shutdown was not working and could create "ghost" consumers on servers restart, that is, consumers that would be listed by the meta leader, but getting information about this consumer would fail. Migration will no longer occur, instead, all R1 pull consumers will be notified that the server is shutting down, invalidating the pending requests (#3576)
  • Consumers on a Limits policy stream could have their replicas changed to R1 (#3576)
  • Ensure that RAFT communication is properly stopped when needed, which otherwise could cause server memory usage increase (#3577)
  • Adding a warning when the inbound of messages causes a lag with the storage layer. In future release, the producers may be notified through a PubAck failure that the message cannot be accepted (#3578)
  • Added pending messages/bytes to pull request errors and status: when the server responds to the client library that a request has timed-out, or server is shutdown, etc..., the response will now include the request pending messages and bytes (#3572, #3587)
  • More messages than the max_msgs_per_subject value could be recovered on server restart following an abnormal server exit (#3579, #3582)
• Leafnode:
  • Existing subscriptions would be sent to leafnodes even though they violated permissions. The publish side would be doing the right thing by not sending the messages over, but the subscription interest was still sent (#3585)
• MQTT:
  • Subjects mapping were not working. Thanks to @​ozon2 for the report (#3552)
• Routing:
  • An implicit route may not reconnect, regardless of the ConnectRetries setting. This can happen in configurations where the routes[] block contains only the seed (and not as a name that could resolve to each IP of the cluster). If a route to a discovered server is disconnected, it may not try to reconnect due to the implicit nature of that connection. Thanks to @​wubumihuo for the report (#3573)

... (truncated)

Commits

• ceebf53 Merge pull request #3597 from nats-io/release_2_9_5
• c16f60a Release v2.9.5
• 32041d9 Merge pull request #3596 from nats-io/js_process_snap
• 55e651c [FIXED] JetStream: processing of snapshot with expired messages
• 56bd22f Merge pull request #3595 from nats-io/max-msgs-per-update
• 1fa5e73 Honor MaxMsgsPerSubject when a stream config is updated, including enforcing ...
• 4f252d3 Merge pull request #3592 from nats-io/fix_flapper
• fe588dc Fixing a flapper
• a0719ec Merge pull request #3591 from aopetrov86/less-optimistic-cache-hit-rate
• 8eb430b add test
• 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 #492.