kjuulh/ceen
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity

Update module github.com/nats-io/nats-server/v2 to v2.9.4 #13

Merged
kjuulh merged 1 commits from renovate/all into main 2022-10-28 11:30:01 +02:00
Conversation 0 Commits 1 Files Changed 2 +3 -1
kjuulh commented 2022-10-28 10:33:46 +02:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
github.com/nats-io/nats-server/v2 require patch v2.9.3 -> v2.9.4

Release Notes

nats-io/nats-server

v2.9.4

Compare Source

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:
  • 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)
Complete Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github.com/nats-io/nats-server/v2](https://github.com/nats-io/nats-server) | require | patch | `v2.9.3` -> `v2.9.4` | --- ### Release Notes <details> <summary>nats-io/nats-server</summary> ### [`v2.9.4`](https://github.com/nats-io/nats-server/releases/tag/v2.9.4) [Compare Source](https://github.com/nats-io/nats-server/compare/v2.9.3...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 [@&#8203;JulienVdG](https://github.com/JulienVdG) for the report ([#&#8203;3583](https://github.com/nats-io/nats-server/issues/3583)) - JetStream: - Possible deadlock. Thanks to [@&#8203;ashumkin](https://github.com/ashumkin) for the report and [@&#8203;neilalexander](https://github.com/neilalexander) for the contribution ([#&#8203;3555](https://github.com/nats-io/nats-server/issues/3555)) - Possible panic in disk full situations. Thanks to [@&#8203;fantashley](https://github.com/fantashley) for the contribution ([#&#8203;3560](https://github.com/nats-io/nats-server/issues/3560), [#&#8203;3568](https://github.com/nats-io/nats-server/issues/3568)) - "First sequence mismatch" after a restart/deployment with streams that have message TTLs. Thanks to [@&#8203;MauriceVanVeen](https://github.com/MauriceVanVeen) for the report ([#&#8203;3567](https://github.com/nats-io/nats-server/issues/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 ([#&#8203;3574](https://github.com/nats-io/nats-server/issues/3574)) - Update of a consumer's `InactiveThreshold` would not always take effect. Thanks to [@&#8203;neilalexander](https://github.com/neilalexander) for the contribution ([#&#8203;3575](https://github.com/nats-io/nats-server/issues/3575)) - A consumer may not be removed based on `InactiveThreshold` in presence of gateways ([#&#8203;3575](https://github.com/nats-io/nats-server/issues/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 ([#&#8203;3576](https://github.com/nats-io/nats-server/issues/3576)) - Consumers on a `Limits` policy stream could have their replicas changed to R1 ([#&#8203;3576](https://github.com/nats-io/nats-server/issues/3576)) - Ensure that RAFT communication is properly stopped when needed, which otherwise could cause server memory usage increase ([#&#8203;3577](https://github.com/nats-io/nats-server/issues/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 ([#&#8203;3578](https://github.com/nats-io/nats-server/issues/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 ([#&#8203;3572](https://github.com/nats-io/nats-server/issues/3572), [#&#8203;3587](https://github.com/nats-io/nats-server/issues/3587)) - More messages than the `max_msgs_per_subject` value could be recovered on server restart following an abnormal server exit ([#&#8203;3579](https://github.com/nats-io/nats-server/issues/3579), [#&#8203;3582](https://github.com/nats-io/nats-server/issues/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 ([#&#8203;3585](https://github.com/nats-io/nats-server/issues/3585)) - MQTT: - Subjects mapping were not working. Thanks to [@&#8203;ozon2](https://github.com/ozon2) for the report ([#&#8203;3552](https://github.com/nats-io/nats-server/issues/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 [@&#8203;wubumihuo](https://github.com/wubumihuo) for the report ([#&#8203;3573](https://github.com/nats-io/nats-server/issues/3573)) ##### Complete Changes </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox. --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzMi4yNDEuMTEiLCJ1cGRhdGVkSW5WZXIiOiIzMi4yNDEuMTEifQ==-->
kjuulh force-pushed renovate/all from d379462ea2 to 89c492501c 2022-10-28 11:03:52 +02:00 Compare
kjuulh merged commit 89c492501c into main 2022-10-28 11:30:01 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kjuulh/ceen#13
No description provided.
Delete Branch "renovate/all"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?