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

[dependabot]

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

Release notes

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

Release v2.8.3

Changelog

Go Version

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

Added

• JetStream:
  • Consumer configuration has now MaxRequestMaxBytes as a int to limit a pull request to that many bytes (#3126)
  • Allow explicit consumer configuration of replica count and memory storage (#3128, #3131)
  • Stream configuration has now RePublish which is a SubjectMapping with a Source and Destination. This enables lightweight distribution of messages to very large number of NATS subscribers (#3129, #3138)
• MQTT:
  • New configuration parameters stream_replicas, consumer_replicas and consumer_memory_storage, which allow the override of the replica count for MQTT streams (which are normally auto-determined base on the cluster size, but capped at 3) and also override the consumer replica count and possibly underlying storage (based on feature added in #3128). Thanks to @​ianzhang1988 for the feedback (#3130)

Improved

• JetStream:
  • Tweak RAFT election timeouts and heartbeats and also reduce lock contention (#3132, #3135)
• Monitoring:
  • A route information in /routez will now include start, last_activity, uptime and idle fields (#3133)

Fixed

• JetStream:
  • Panic due to non loaded message cache during a file compaction (#3110)
  • Downstream sourced retention policy streams during server restart have redelivered messages (#3109, #3122)
  • Possible lockup due to a missing mutex unlock in some conditions (#3115)
  • Panic when processing a consumer create in clustered mode. This was introduced in v2.8.2 (#3117)
  • Some data races (#3120, #3134)
  • Panic runtime error: makeslice: cap out of range on server restart. Thanks to @​ajlane for the report (#3121)
  • A purge with a given subject and a sequence of 1 for a stream with a single message would not work (#3121)
  • Some JS API requests handled through routes or gateways may be dropped when there were too many of them at once (#3142)
  • Consumer with "deliver new" delivery mode could skip messages in some conditions after a consumer step down or server(s) restart (#3143)
• MQTT:
  • Errors deleting consumers will now prevent deletion of the session record, which would otherwise leave orphan consumers. Thanks to @​ianzhang1988 for the report (#3144)
• Accounts Export/Import isolation with overlap subjects. Thanks to @​JH7 for the report (#3112)

Complete Changes

nats-io/nats-server@v2.8.2...v2.8.3

Release v2.8.2

Changelog

Go Version

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

Added

... (truncated)

Commits

• 7e9b604 Merge pull request #3146 from nats-io/release_2_8_3
• f423f07 Release v2.8.3
• 0ebc1cc Merge pull request #3143 from nats-io/js_cons_dlv_new_restart_or_step_down
• 53e3c53 [FIXED] JetStream: consumer with deliver new may miss messages
• 65094c4 Merge pull request #3142 from nats-io/js_routed_api_reqs
• 4735932 Merge pull request #3144 from nats-io/mqtt_del_cons_errors
• 66b1b51 [FIXED] MQTT: Errors deleting consumers will now prevent deletion of session
• 4bf8142 [FIXED] Fast routed JetStream API requests were dropped
• 7512960 Merge pull request #3137 from nats-io/consumer_num_pending
• 790d643 Consumer's num pending can now rely on the stream's store vs trying to mainta...
• 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 #378.