Update module github.com/nats-io/nats-server/v2 to v2.9.3 - autoclosed #2
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/github.com-nats-io-nats-server-v2-2.x"
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?
This PR contains the following updates:
v2.8.4
->v2.9.3
Release Notes
nats-io/nats-server
v2.9.3
Compare Source
Changelog
Go Version
Fixed
-help
section. Thanks to @ariel-zilber for the contributions (#3523, #3527)Complete Changes
v2.9.2
Compare Source
Changelog
Go Version
Improved:
v2.8.4
andv2.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 tov2.8.4
(#3504)Fixed
js.UpdateConsumer()
(using the Golang client library) with a replica of 1, the call would timeout but the operation would actually succeed (#3502)Complete Changes
v2.9.1
Compare Source
Changelog
Go Version
Added
meta_cluster
ofstatsz
orjsz
monitoring endpoint (#3476)discard_new_per_subject
can now be set (along with discard new policy and max messages per subject > 0) (#3487)Improved
Updated
Changed
Fixed
Name
andDurable
are not equal when sending to the new$JS.API.CONSUMER.CREATE.%s.%s.%s
subject (#3471)409
to the client library when a pull request was closed after sending at least a message but could not send more if that would exceed themax_bytes
pull request limit (#3474)websocket{}
block had ano_auth_user
defined, this user was not being used for the account binding for that leaf node connection (#3489){{Split()}}
subject mapping function (#3463)Complete Changes
v2.9.0
Compare Source
Changelog
IMPORTANT NOTE: Leafnode connections will now be closed if the cluster name is detected to be the same on the "hub" and "spoke", and reconnect attempts will be delayed by 30 seconds. If you are unaware of this misconfiguration you may experience a split network for longer than expected during the upgrade process. See the
CHANGED
section below and more details in pull request #3232.Go Version
Added
AllowDirect
allows capable client libraries to have a new API that retrieves a message from any member of the group (leader or replicas). Note that this can lead to non-coherent reads after write since a replica may respond to the request although that replica does not yet have the latest write. The configuration fieldMirrorDirect
allow the mirror to be part of the origin's group (#3158, #3221, #3238, #3247, #3252, #3325, #3329, #3358, #3380, #3392, #3441)InactiveThreshold
for durable consumers. If the inactivity threshold is specified, a durable that is offline for more than this duration will be removed (#3190)$JS.API.ACCOUNT.PURGE.<account name>
. Thanks to @goku321 and @sourabhaggrawal for the report (#3319, #3378)jetstream: { max_outstanding_catchup: 32MB }
. This limit is how many bytes in total may be inflight during streams catchup. This can help lower network bandwidth saturation (#3418)StreamInfo
requests. Note that not all clients may have the ability to provide the offset at the time of the server release (#3454)SignatureHandler
in remote configurations. This is applicable to applications embedding the NATS Server. Thanks to @kung-foo for the suggestion (#3335)$SYS.ACCOUNT.%s.SERVER.CONNS
message response (#3187)/accstatz
to get specific account statistics (such as number of connections, messages/bytes in/out, etc...) (#3250, #3382)/healthz
endpoint is now also available via the system account under the$SYS.REQ.SERVER.PING.HEALTHZ
subject (#3250)/healthz
endpoint:/healthz?js-enabled=true
to return an error if JetStream is disabled, and/healthz?js-server-only=true
to skip the check of JetStream accounts, streams and consumers. Thanks to @mfaizanse for the contribution (#3326)/connz?auth=1
endpoint now includes atls_peer_certs
array with subject, subject public key and raw certificate sha256. Thanks to @RedShift1 for the suggestion (#3387)/jsz?accounts=true
endpoint will now show non 0 values forreserved_memory
andreserved_storage
when applicable (#3435)consumer_inactive_threshold
allow new QoS1 consumers to be removed if they are offline for more than the specified duration (based on #3190) (#3193)GOMAXPROCS
to match Linux container CPU quota. Thanks to @1995parham for the contribution (#3218, #3224, #3237, #3406)DontListen
that triggers the server to accept only "in memory" client connections. This is for embedded use-cases only and is paired with changes made in the client library nats.go. Thanks to @neilalexander for the contribution (#2360, #3225)DisallowBearer
(#3127)/usr/bin
instead of/usr/local/bin
as it used to. We now have added symlink to/usr/local/sbin
. Thanks to @ismail0352 for the report (#3242)SplitFromLeft
,SplitFromRight
,SliceFromLeft
,SliceFromRight
andSplit
(#3305)s390x
architecture (#3458)Changed
RePublish
configuration field is now a newRePublish
object (andSubjectMapping
has been removed) that allows for a new boolean field calledHeadersOnly
. This could be useful for large messages and having republish just be a signaling mechanism (#3157)Nats-Expected-Last-Sequence
with a0
value. The server used to ignore if the sequence was 0, but now it will treat it as a requirement that the stream be empty if the header is present with a value of0
. Thanks to @bruth for the suggestion (#3038)_sys_
is now reserved and an application attempting to use it would get a permission violation (#3246)Improved
$JS.API.CONSUMER.CREATE.<stream>.<subject>.<filter>
(#3409)max-bytes
for pull consumers (#3456)Trusted Operators
now displays theExpires
date asNever
instead of the epoch time. Thanks @mschneider82 for the contribution (#3452)Updated
AckAll
andNoAck
are now allowed on pull consumers (#3442)Fixed
leafnodes
block would contain anauthorization{}
block, even if no modification was done there. Thanks to @cleaton for the report (#3204)Nate-Subject
header - similar to stream direct get messages (#3169)InactiveThreshold
interval (#3229)MaxAckPending
, expire all pull requests that had at least 1 delivered message (#3241)unique_tag
configuration (#3248)RePublish
configuration would republish any incoming message, regardless of theRePublish
's source subject (#3271)MaxWaiting
configuration since it is not currently supported (#3302)RePublish
configuration since it is not currently supported (#3328)Nats-Expected
headers, such as concurrent uses of kv.Create()/kv.Delete() (#3400)"foo.*", "foo.bar"
would create duplicate messages if produced onfoo.bar
and will now be reported as an invalid configuration (#3429)offline
in some situations (#3433)Complete Changes
Configuration
📅 Schedule: 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.
This PR has been generated by Renovate Bot.
Update module github.com/nats-io/nats-server/v2 to v2.9.3to Update module github.com/nats-io/nats-server/v2 to v2.9.3 - autoclosedPull request closed