-
### Observed behavior
`async_nats::connect` ignores all options in nats url and use default options
### Expected behavior
parse options from url
### Server and client version
bug is in crate `asy…
-
### Observed behavior
Creating a Mirrored stream using a source that contains messages with `Nats-Expected-Last-Subject-Sequence` headers still performs sequence checks as per the source stream onc…
-
// when
$ nats pub --count=100000 -s nats://nats:foliage@nats:4222 functions.graph.api.query.jpgql.dcra.root "{\"payload\":{\"query_id\":\"QUERYID\", \"jpgql_query\":\".type1.*.*[tags('t1') || tags…
-
### Observed behavior
I have two NATS Clusters each with 4 Node.
ClusterA
node1a.cluster.svc.local
node2a.cluster.svc.local
node3a.cluster.svc.local
node4a.cluster.svc.local
Load Balancer :- …
-
# Observed behavior
Given a hub and leaf setup, once a leaf has been established a local mirror of an hub stream, publishing a message with a header **Nats-Expected-Stream** results in a leaf deliv…
-
### Observed behavior
When using the `allow_responses` map in user permissions with `max` set, request/reply takes a significant performance hit depending on the value of `expires`. If the `max` valu…
-
### Observed behavior
If we publish 30 messages, the subscriber gets only 25-27 messages rather than 30.
### Expected behavior
The subscriber should receive an exact number of messages as published…
-
been playing with ergo - it’s great .
Just wonder if you would consider a NATS driver in addition to the existing kafka one you use ?
NATS is like Kafka, but pure go.
https://github.com/nat…
-
Ordered consumer performance is our gold standard benchmark for consumers. Test and improve ordered consumer performance. This might inline with planned efforts to improve receive buffer performance.
…
-
### Observed behavior
Performance degradation after the slow consumer connection.
As you can see below, we are observing about 30% degradation of the incoming messages when the slow consumer conn…