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

[dependabot]

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

Release notes

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

Release v2.8.4

Changelog

Go Version

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

Fixed

• JetStream:
  • Consumer pending count was not correct when a stream had max messages per subject greater than 1 and a consumer that filtered out part of the stream was created (#3148)
  • Spurious 408 status messages sent to pull consumers. Also made some modifications to reduce lock contention between processing of acknowledgments and delivery of messages (#3149)
• MQTT:
  • Connections with same client ID but on different domains may have been detected as duplicates (#3150)

Complete Changes

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

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). Note: This feature is not compatible or tested in conjunction with modifying the associated stream's replication factor once created (2.7.3+).
  • EXPERIMENTAL FEATURE: 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)

... (truncated)

Commits

• 66524ed Merge pull request #3152 from nats-io/release_2_8_4
• de52c0b Release v2.8.4
• a52f126 Bump version to v2.8.4-beta.2 and fix flapper
• 1c984d4 Merge pull request #3150 from nats-io/mqtt_sess_diff_domains
• b344519 [FIXED] MQTT: Same session ID in different domains were considered duplicates
• 72ed48d Merge pull request #3149 from nats-io/pull_perf_stable
• d69394e Fix spurious 408s under load and move processing of acks to their own Go rout...
• 752c0ad Merge pull request #3148 from nats-io/max_msgs_per_num_pending_bug
• 46f7f7b Consumer pending was not correct when stream had max msgs per subject set > 1...
• 7bdd679 Bump version to dev v2.8.4-beta
• 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 #447.